From: Junio C Hamano <gitster@pobox.com>
To: david@lang.hm
Cc: Elijah Newren <newren@gmail.com>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org, Stephan Beyer <s-beyer@gmx.net>
Subject: Re: Is incremental staging really the common mode?
Date: Sun, 07 Sep 2008 17:40:20 -0700 [thread overview]
Message-ID: <7v1vzvjwqz.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0809071729310.8096@asgard.lang.hm> (david@lang.hm's message of "Sun, 7 Sep 2008 17:32:09 -0700 (PDT)")
david@lang.hm writes:
> also, how many are doing 'git add .' or 'git add *' followed by git
> commit?
Everybody who starts a new history from scratch from an existing tarball
would be doing this at least once ;-)
> there were several commands listed that I have never heard of before
> and will want to research to see what they do to see if I should be
> using them.
The commands singled out were either (1) ancient, nobody should be using
them, and we would love to prove that nobody is using them anymore so that
we can remove them, or (2) reasonably new inventions that would help
common situations more than the stock Porcelain we have had for years, to
see if they are already widely adopted.
Perhaps somebody (or group of people, taking turns) should post a "git
trick of the week" series to this mailing list?
next prev parent reply other threads:[~2008-09-08 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 20:17 Is incremental staging really the common mode? [Was: Re: Git User's Survey 2008 partial summary, part 4 - how do we use Git] Elijah Newren
2008-09-08 0:32 ` david
2008-09-08 0:40 ` Junio C Hamano [this message]
2008-09-08 0:45 ` Is incremental staging really the common mode? david
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=7v1vzvjwqz.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=newren@gmail.com \
--cc=s-beyer@gmx.net \
/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).