From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Re: [PATCH 3/5] Add more working files, directories to .gitignore
Date: Sat, 22 Mar 2014 10:47:13 -0700 [thread overview]
Message-ID: <20140322104713.5adf9577.dolsen@gentoo.org> (raw)
In-Reply-To: <20140305153246.GG25297@odin.tremily.us>
On Wed, 5 Mar 2014 07:32:46 -0800
"W. Trevor King" <wking@tremily.us> wrote:
> On Tue, Mar 04, 2014 at 09:17:42PM -0800, Brian Dolbec wrote:
> > On Tue, 4 Mar 2014 20:50:38 -0800, W. Trevor King wrote:
> > > On Sun, Mar 02, 2014 at 03:01:00PM -0800, Brian Dolbec wrote:
> > > These all look like entries for a local $GIT_DIR/info/exclude,
> > > instead of the shared, in-tree .gitignore, since they're specific
> > > to your workflow and not catalyst or it's build process.
> >
> > Yes, they are. I've never professed to be a git "expert"
> > Please enlighten me on that. It's annoying trying to wade through
> > all those files making commits.
>
> The “DESCRIPTION” section of gitignore(5) goes through it pretty
> clearly [1]. $GIT_DIR/info/exclude (likely
> ~/src/catalyst/.git/info/exclude or similar for you) has the same
> syntax as .gitignore, but it's not versioned. gitignore(5) recommends
> it for [1]:
>
> Patterns which are specific to a particular repository but which do
> not need to be shared with other related repositories (e.g.,
> auxiliary files that live inside the repository but are specific to
> one user’s workflow)
>
> Cheers,
> Trevor
>
> [1]: https://www.kernel.org/pub/software/scm/git/docs/gitignore.html
>
Done, that you for that info This commit is removed from pending, will
push once some other feedback changes are finished testing.
--
Brian Dolbec <dolsen>
next prev parent reply other threads:[~2014-03-22 17:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 23:00 [gentoo-catalyst] [PATCH 2/5] generic_stage_target.py: Fix an intermittent snapshot_cache_path keyerror Brian Dolbec
2014-03-02 23:01 ` [gentoo-catalyst] [PATCH 3/5] Add more working files, directories to .gitignore Brian Dolbec
2014-03-03 3:07 ` Brian Dolbec
2014-03-05 4:50 ` [gentoo-catalyst] " W. Trevor King
2014-03-05 5:17 ` Brian Dolbec
2014-03-05 15:32 ` W. Trevor King
2014-03-22 17:47 ` Brian Dolbec [this message]
2014-03-02 23:01 ` [gentoo-catalyst] [PATCH 4/5] catalyst/targets/generic_target.py: Pass TERM through to the chroot Brian Dolbec
2014-03-08 18:38 ` W. Trevor King
2014-03-02 23:01 ` [gentoo-catalyst] [PATCH 5/5] Add arm64 support Brian Dolbec
2014-03-03 3:05 ` Brian Dolbec
2014-03-05 4:47 ` [gentoo-catalyst] Re: [PATCH 2/5] generic_stage_target.py: Fix an intermittent snapshot_cache_path keyerror W. Trevor King
2014-03-05 5:25 ` Brian Dolbec
2014-03-08 18:25 ` [gentoo-catalyst] [PATCH] generic_stage_target: Don't set mountmap['portdir'] without SNAPCACHE W. Trevor King
2014-03-22 22:39 ` Brian Dolbec
2014-03-24 5:08 ` W. Trevor King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140322104713.5adf9577.dolsen@gentoo.org \
--to=dolsen@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox