From: Andreas Schwab <schwab@linux-m68k.org>
To: Unknown <unknown@unknown.invalid>
Cc: git@vger.kernel.org
Subject: Re: Help requested - trying to build a tool doing whole-tree commits
Date: Fri, 09 Nov 2012 22:50:17 +0100 [thread overview]
Message-ID: <m2txsyqwdi.fsf@igel.home> (raw)
In-Reply-To: <20121109182024.81074BC66D4@golux> (unknown@unknown.invalid's message of "Fri, 9 Nov 2012 13:20:24 -0500 (EST)")
Unknown <unknown@unknown.invalid> writes:
> I need a command or command sequence that will commit an entire file
> tree to a repository...
>
> (a) Allowing me to specify committer and author metadata, and
>
> (b) deleting paths not present in the previous commit on the current
> branch, and
>
> (c) allowing me to specify merge links from other previous commits.
>
> git commit -a passes (a) and (b) but not (c).
git commit -a won't add new files, so you probably want to use git add
-A && git commit. I'm not quite sure what you mean with "merge links",
but if you want to create merge commits the you'll need to resort to
plumbing: git add -A && git write-tree && git commit-tree && git
update-ref.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-11-09 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 18:20 Help requested - trying to build a tool doing whole-tree commits Unknown, Eric S. Raymond
2012-11-09 21:50 ` Andreas Schwab [this message]
2012-11-10 19:24 ` Felipe Contreras
2012-11-10 16:57 ` Junio C Hamano
2012-11-11 14:47 ` Eric S. Raymond
[not found] <931951238.74665890.1352725212354.JavaMail.root@zimbra39-e7.priv.proxad.net>
2012-11-12 13:11 ` ydirson
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=m2txsyqwdi.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=unknown@unknown.invalid \
/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.