git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Alan Chandler <alan@chandlerfamily.org.uk>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] make 'git add' a first class user friendly interface to the index
Date: Fri, 01 Dec 2006 21:01:04 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0612012056420.9647@xanadu.home> (raw)
In-Reply-To: <200612020018.32672.alan@chandlerfamily.org.uk>

On Sat, 2 Dec 2006, Alan Chandler wrote:

> On Friday 01 December 2006 22:31, Junio C Hamano wrote:
> > Nicolas Pitre <nico@cam.org> writes:
> ...
> >
> > > +Contrary to other SCMs, with GIT you have to explicitly "add" all the
> > > +changed file content you want to commit together to form a changeset
> > > +with the 'add' command before using the 'commit' command.
> >
> > ... "before a new commit is made"; it is not an offence to leave
> > local changes outside the index.  Staging such changes to all
> > files is done using the "-a" flag and that is done "before a new
> > commit is made", but not "before using the 'commit' command" --
> > it is done at the same time.

Bleamphfff...  Nah.  There is certainly another way to formulate that.

> How about
> 
> Contrary to other SCM's, with GIT you have to explicitly "add" the content 
> that you want to commit before it is made; it is not an offence to leave 

Before what is made?

> changes outside the index if you want to leave them to a later commit.  
> However if you do want all changes from your working tree to be added to the 
> commit before it is made use the "-a" flag with the commit command and the 
> content will be added just before the commit is made.

Nah.  Too many concepts in the same paragraph.



  reply	other threads:[~2006-12-02  2:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01 20:06 [PATCH] make 'git add' a first class user friendly interface to the index Nicolas Pitre
2006-12-01 22:31 ` Junio C Hamano
2006-12-02  0:18   ` Alan Chandler
2006-12-02  2:01     ` Nicolas Pitre [this message]
2006-12-02  3:05   ` Nicolas Pitre
2006-12-02  6:54   ` Carl Worth
2006-12-02  7:54     ` Junio C Hamano
2006-12-02  9:06       ` Carl Worth
2006-12-02 10:11       ` Jakub Narebski
2006-12-02 14:51         ` Han-Wen Nienhuys
2006-12-02  8:28     ` Alan Chandler
2006-12-02 16:49       ` Carl Worth
2006-12-02 17:12         ` Jakub Narebski
2006-12-02 18:05         ` Alan Chandler
2006-12-03  4:04           ` Nicolas Pitre
2006-12-03  4:22         ` Nicolas Pitre
2006-12-03  4:34       ` Nicolas Pitre
2006-12-02  9:52   ` Jakub Narebski
2006-12-03  5:03   ` Nicolas Pitre
2006-12-03  5:33 ` [PATCH v2] " Nicolas Pitre
2006-12-03  9:16   ` Alan Chandler

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=Pine.LNX.4.64.0612012056420.9647@xanadu.home \
    --to=nico@cam.org \
    --cc=alan@chandlerfamily.org.uk \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).