From: Peter Baumann <peter.baumann@gmail.com>
To: git@vger.kernel.org
Subject: Can't export whole repo as patches
Date: Fri, 7 Apr 2006 20:47:01 +0200 [thread overview]
Message-ID: <20060407184701.GA6686@xp.machine.de> (raw)
I'd like to export the whole history of a project of mine via patches
but I can't get the inital commit.
How can I get the inital commit as a patch?
That's what I tried:
git --version
git version 1.2.4 # debian sarge
mkdir /tmp/testrepo && cd /tmp/testrepo
git-init-db
echo a > a_file.txt
git-add a_file.txt
git-commit -a -m "a_file added"
echo b >> a_file.txt
git-commit -a -m "a_file modifed"
xp:/tmp/testrepo git-format-patch master~1
0001-a_file-modified.txt
cat 0001-a_file-modified.txt
From nobody Mon Sep 17 00:00:00 2001
From: Peter Baumann <peter.baumann@gmail.com>
Date: Fri Apr 7 12:20:54 2006 +0200
Subject: [PATCH] a_file modified
---
a_file.txt | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
d8ceeed82a29004c066a98e0d390818e65fa9da7
diff --git a/a_file.txt b/a_file.txt
index 7898192..422c2b7 100644
--- a/a_file.txt
+++ b/a_file.txt
@@ -1 +1,2 @@
a
+b
--
1.2.4
As you can see, there is only a patch of the second commit. But it seems that
this behaviour is correct, because I asked for the diff between master^..master
Obviously, I wanted a way to get the diff of master~2..master.
Trying harder:
git-format-patch master~2
Not a valid rev master~2 (master~2..HEAD)
Any hint to the correct way is appreciated.
</me thinking loudly>
The best would be if git would have an implicit tag or branch called "init"
(name doesn't really matter) which is the root of an empty repository. In that case
one can do git-format-patch root..master and it would the right thing.
Greetings,
Peter Baumann
next reply other threads:[~2006-04-07 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 18:47 Peter Baumann [this message]
2006-04-07 19:18 ` Can't export whole repo as patches Junio C Hamano
2006-04-08 18:02 ` How to create independent branches Peter Baumann
2006-04-08 18:28 ` Jakub Narebski
2006-04-09 8:11 ` Peter Baumann
2006-04-09 8:22 ` Peter Baumann
2006-04-08 20:49 ` Junio C Hamano
2006-04-08 20:57 ` Petr Baudis
2006-04-08 21:00 ` Junio C Hamano
2006-04-08 22:09 ` Johannes Schindelin
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=20060407184701.GA6686@xp.machine.de \
--to=peter.baumann@gmail.com \
--cc=git@vger.kernel.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 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.