From: Markus Heidelberg <markus.heidelberg@web.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Santi Béjar" <santi@agolina.net>, "Jeff King" <peff@peff.net>,
"Nguydn Thái Ngdc" <pclouds@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 1/2] init: support --import to add all files and commit right after init
Date: Sat, 28 Mar 2009 11:58:50 +0100 [thread overview]
Message-ID: <200903281158.51012.markus.heidelberg@web.de> (raw)
In-Reply-To: <alpine.DEB.1.00.0903270259470.10279@pacific.mpi-cbg.de>
Johannes Schindelin, 27.03.2009:
> Others who want to have a quick way to work safely with something they
> might need to change, and might then want to use the full power of Git to
> see what they changed. Without any need for a "nice" first commit.
What's the difference between the first commit and the others? I don't
see the reason, not to have a short description for it.
Markus
next prev parent reply other threads:[~2009-03-28 11:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 10:58 [PATCH 1/2] init: support --import to add all files and commit right after init Nguyễn Thái Ngọc Duy
2009-03-25 11:35 ` Jeff King
2009-03-25 22:54 ` Nguyen Thai Ngoc Duy
2009-03-25 11:56 ` Santi Béjar
2009-03-25 12:38 ` Johannes Schindelin
2009-03-25 12:42 ` Jeff King
2009-03-25 12:49 ` Santi Béjar
2009-03-26 21:23 ` Markus Heidelberg
2009-03-27 2:03 ` Johannes Schindelin
2009-03-27 5:06 ` Jeff King
2009-03-27 5:08 ` Jeff King
2009-03-28 10:58 ` Markus Heidelberg [this message]
2009-03-28 12:39 ` Johannes Schindelin
2009-03-28 13:09 ` Markus Heidelberg
-- strict thread matches above, loose matches on Subject: below --
2009-03-26 10:10 Nguyễn Thái Ngọc Duy
2009-03-26 10:13 ` Jeff 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=200903281158.51012.markus.heidelberg@web.de \
--to=markus.heidelberg@web.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=santi@agolina.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 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.