All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Add .gitignore files
Date: Tue, 27 Feb 2007 08:01:31 +0100	[thread overview]
Message-ID: <200702270801.32420.sr@denx.de> (raw)
In-Reply-To: <528646bc0702262242h64d834a2u5750942983b59bbe@mail.gmail.com>

On Tuesday 27 February 2007 07:42, Grant Likely wrote:
> > > There is a strongly established workflow convention use by other
> > > git-using projects.  The workflow for committing is this:
> > > $ git-status   # to show what has changed/added/removed
> > > $ git-update-index   # as needed to update the index
> > > $ git-commit    # make it real;
> > > It should be noted that 'make clean' is not a required step for the
> > > commit workflow.
> > >
> > > Alternately, the same thing is done with cogito:
> > > $ cg-status
> > > $ cg-commit
> >
> > I can do this fine even with uncleanded files. cg-commit will not anny
> > files that have not been added with cg-add.
> >
> > Is this different with above sequence of git commands?
>
> No it's not different.  Your right.  New files must always be
> explicitly added.

If I understand it correctly, then the main usage difference between you (core 
git users) and Wolfgang (and me by the way) cogito users, is the handling of 
new files. With git-update-index all new files are added to the index 
automatically (without parameters), right? Using cg-add you have to either 
name the files explicitly you want to add, or use the "-a" option.

Even as cogito user (and I'm thinking again about switching to using the core 
git commands more and more), I vote for adding this .gitignore file, since it 
really seems to be needed in this workflow. And we want to make it as easy 
for most of the people to work on this project.

> > You leave me no sane way out but to give in, but at least I  want  to
> > understand why all this is needed. I don't get it yet.
>
> Hehehe, I probably owe you like 10 beers to offset some of the debates
> I've instigated lately.  Are you going to be able to make it to OLS
> this year?

Could be that I will make it this year. Perhaps I can act here as 
Wolfgangs "substitute"? ;-)

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
=====================================================================

  reply	other threads:[~2007-02-27  7:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20 23:26 [U-Boot-Users] [PATCH] Add .gitignore files Timur Tabi
2007-02-20 23:47 ` Grant Likely
2007-02-26 13:15   ` Wolfgang Denk
2007-02-26 16:58     ` Timur Tabi
2007-02-26 21:38       ` Wolfgang Denk
2007-02-26 21:46         ` Timur Tabi
2007-02-26 22:00           ` Jerry Van Baren
2007-02-27  0:35         ` Grant Likely
2007-02-27  1:19           ` Andy Fleming
2007-02-27  1:25           ` Wolfgang Denk
2007-02-27  1:40             ` Andy Fleming
2007-02-27  6:42             ` Grant Likely
2007-02-27  7:01               ` Stefan Roese [this message]
2007-02-27  7:15                 ` Grant Likely
2007-02-27  7:33                   ` Stefan Roese
2007-02-27  7:42                     ` Grant Likely
2007-02-27 14:56                 ` Timur Tabi
2007-02-27 15:48                   ` Kumar Gala
2007-02-27 22:30                   ` Haavard Skinnemoen
2007-02-26 17:54     ` Scott Wood
2007-02-26 13:11 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2007-09-05 14:01 Grant Likely

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=200702270801.32420.sr@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.