From: Gerhard Wiesinger <lists@wiesinger.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: kusmabite@gmail.com, Thomas Rast <trast@student.ethz.ch>,
git@vger.kernel.org
Subject: Re: Global .git directory
Date: Wed, 28 Apr 2010 22:10:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1004282204430.29101@bbs.intern> (raw)
In-Reply-To: <l2i81b0412b1004280101ga2335a58z37d97295ab6c88e7@mail.gmail.com>
On Wed, 28 Apr 2010, Alex Riesen wrote:
> On Wed, Apr 28, 2010 at 07:33, Gerhard Wiesinger <lists@wiesinger.com> wrote:
>> On Tue, 27 Apr 2010, Erik Faye-Lund wrote:
>>> Please see Documentation/SubmittingPatches. It's difficult to
>>> comment on a non-inlined patch.
>>
>> Patch done on top of HEAD.
>
> The patches "done on top of HEAD" are usually useless for
> everyone, including the submitter. HEAD changes over time.
> for instance I wont be able to apply your patches on my HEAD,
> as I have a lot of changes in my Git repo.
>
> If you about to share your modifications, you better base your
> changes on stable points in history, like releases (marked by
> release tags, like "v1.7.1").
>
Patch is made on top of v1.7.1 (it was HEAD at the time of the last pull)
according to git log.
>> BTW2:
>> Why is it necessary to do:
>
> It is so you can distinguish between the changes in progress and
> the changes ready to be submitted (prepared for commit).
>
>> # Displays only changed files
>> git diff
>
> To be exact: the changes not yet staged for commit.
>
>> # Displays only added files
>> git diff --cached
>
> No, it displays the changes ready to be committed (staged).
>
>> I would like to have a full diff of my changes:
>> git diff -a
>
> You wouldn't use it. It is very useful to separate the phases of workflow.
>
> BTW, try using "git status". It'll show you both lists of changed files.
> Also "git gui", and "gitk" make the lists visible ("git gui" is more like
> "git status", and you can commit from it).
>
>> (or better "git diff -a" should be the default behaviour, I think that's
>> very confusing for new users)
>
> Only to unwilling to learn. You'd be probably the first to suggest
> to combine the two stages of change. Usually people understand
> (or get a feeling of understanding) the index even before they send
> first mail to the mailing list.
Ok, as explained in previous mail, confusion was introduced from the
tutorial at: http://git.or.cz/course/svn.html
Thnx for explaination so far.
Ciao,
Gerhard
--
http://www.wiesinger.com/
next prev parent reply other threads:[~2010-04-28 20:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 5:14 Global .git directory Gerhard Wiesinger
2010-04-27 9:59 ` Thomas Rast
2010-04-27 20:06 ` Gerhard Wiesinger
2010-04-27 20:26 ` Erik Faye-Lund
2010-04-28 5:33 ` Gerhard Wiesinger
2010-04-28 6:22 ` Tomas Carnecky
2010-04-28 20:03 ` Gerhard Wiesinger
2010-04-28 8:01 ` Alex Riesen
2010-04-28 20:10 ` Gerhard Wiesinger [this message]
2010-04-28 12:50 ` Erik Faye-Lund
2010-04-28 20:22 ` Gerhard Wiesinger
2010-05-04 5:07 ` Gerhard Wiesinger
2010-05-04 5:40 ` Andrew Ruder
2010-05-04 6:02 ` Andreas Ericsson
2010-05-04 6:07 ` Gerhard Wiesinger
2010-05-04 16:55 ` Junio C Hamano
2010-04-27 20:37 ` Jacob Helwig
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=alpine.LFD.2.00.1004282204430.29101@bbs.intern \
--to=lists@wiesinger.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=raa.lkml@gmail.com \
--cc=trast@student.ethz.ch \
/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).