From: Miklos Vajna <vmiklos@frugalware.org>
To: jidanni@jidanni.org
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Documentation/gitcore-tutorial.txt: HEAD not symlink these days
Date: Tue, 6 Jan 2009 09:57:27 +0100 [thread overview]
Message-ID: <20090106085727.GG21154@genesis.frugalware.org> (raw)
In-Reply-To: <87ljtpnoag.fsf@jidanni.org>
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
On Tue, Jan 06, 2009 at 10:47:35AM +0800, jidanni@jidanni.org wrote:
> OK please change it for me, as today is my junior patching practice
> day, and a patch to a patch is way over my head.
I can, but in the longer term, I think it's better if you learn to use
git rebase -i / git commit --amend. You can do it tomorrow as well.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-01-06 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 2:18 [PATCH] Documentation/gitcore-tutorial.txt: HEAD not symlink these days jidanni
2009-01-06 2:44 ` Miklos Vajna
2009-01-06 2:47 ` jidanni
2009-01-06 8:57 ` Miklos Vajna [this message]
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=20090106085727.GG21154@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jidanni@jidanni.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).