A chapter about this topic has been added recently.
Signed-off-by: Miklos Vajna <redacted>
---
i forgot to include this change in my previous patch, so here is the
correction.
Documentation/user-manual.txt | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
@@ -4277,5 +4277,3 @@ Write a chapter on using plumbing and writing scripts. Alternates, clone -reference, etc. git unpack-objects -r for recovery--submodules
On Tue, Sep 25, 2007 at 03:49:36PM -0400, "J. Bruce Fields" [off-list ref] wrote:
And there's a ton of other stuff on that todo list if you're looking to
make more "noise"--patches always welcomed....
i was this in the todo:
"Add a section on working with other version control systems, including
CVS, Subversion, and just imports of series of release tarballs."
to questions:
1) does this include documentation about git-svn? i mean a howto similar
to the submodules chapter.
2) does it worth to document a typical usage of tailor? we used it a lot
when converting from darcs to git and once you figure out the right
options, it's really easy to use it. but maybe it's unrelated.
thanks,
- VMiklos
From: J. Bruce Fields <hidden> Date: 2016-06-15 22:43:36
On Tue, Sep 25, 2007 at 09:57:31PM +0200, Miklos Vajna wrote:
i was this in the todo:
"Add a section on working with other version control systems, including
CVS, Subversion, and just imports of series of release tarballs."
to questions:
1) does this include documentation about git-svn? i mean a howto similar
to the submodules chapter.
Could be. Though when I used it I thought the git-svn manpage was
actually very good, so I'd be tempted to just point to that.
2) does it worth to document a typical usage of tailor? we used it a lot
when converting from darcs to git and once you figure out the right
options, it's really easy to use it. but maybe it's unrelated.
I think we should try to keep the git documentation mostly confined to
tools that are distributed with git itself. So it might be worth a few
words just to mention the existance of tailor and how it compares to
other tools, but I'd leave it at that.
--b.
From: J. Bruce Fields <hidden> Date: 2016-06-15 22:43:36
On Tue, Sep 25, 2007 at 04:02:52PM -0400, bfields wrote:
I think we should try to keep the git documentation mostly confined to
tools that are distributed with git itself. So it might be worth a few
words just to mention the existance of tailor and how it compares to
other tools, but I'd leave it at that.
So in fact it might be that what's needed isn't any new documentation on
the available tools with their features and limitations.
I know that when I recently had to deal with a svn tree the hardest part
was figuring out where to start (git-svn? git-svnimport?). I seem to
recall threads here suggesting this is a general problem.
One exception--the "series of tarballs" thing--I think it's cool that
you can just unpack a bunch of tarballs and string them together into a
git history. It gives a good sense of how git works, and I don't think
it's documented explicitly anywhere. I think that might be kinda fun to
write up. But I haven't tried.
--b.
From: J. Bruce Fields <hidden> Date: 2016-06-15 22:43:36
On Tue, Sep 25, 2007 at 04:13:06PM -0400, J. Bruce Fields wrote:
On Tue, Sep 25, 2007 at 04:02:52PM -0400, bfields wrote:
quoted
I think we should try to keep the git documentation mostly confined to
tools that are distributed with git itself. So it might be worth a few
words just to mention the existance of tailor and how it compares to
other tools, but I'd leave it at that.
So in fact it might be that what's needed isn't any new documentation on
the available tools with their features and limitations.
(Uh, I meant to say: "isn't any new documentation on individual tools,
but rather a list of the available tools with their features and
limitations.")
I know that when I recently had to deal with a svn tree the hardest part
was figuring out where to start (git-svn? git-svnimport?). I seem to
recall threads here suggesting this is a general problem.
One exception--the "series of tarballs" thing--I think it's cool that
you can just unpack a bunch of tarballs and string them together into a
git history. It gives a good sense of how git works, and I don't think
it's documented explicitly anywhere. I think that might be kinda fun to
write up. But I haven't tried.
--b.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signed-off-by: Miklos Vajna <redacted>
---
On Tue, Sep 25, 2007 at 04:13:06PM -0400, "J. Bruce Fields" [off-list ref] wrote:
One exception--the "series of tarballs" thing--I think it's cool that
you can just unpack a bunch of tarballs and string them together into a
git history. It gives a good sense of how git works, and I don't think
it's documented explicitly anywhere. I think that might be kinda fun to
write up. But I haven't tried.
@@ -978,6 +978,19 @@ $ git add . # include everything below ./ in the first commit: $ git commit -------------------------------------------------+If you already have a series of tarballs (typically previous releases without+using a version control system):++-------------------------------------------------+$ mkdir project+$ cd project+$ git init+$ perl import-tars.perl /path/to/tarballs/*.tar.bz2+$ git checkout import-tars+-------------------------------------------------++You can find `import-tars.perl` in the `contrib/fast-import/` directory.+ [[how-to-make-a-commit]] How to make a commit --------------------
From: J. Bruce Fields <hidden> Date: 2016-06-15 22:43:36
On Wed, Sep 26, 2007 at 12:37:04AM +0200, Miklos Vajna wrote:
Signed-off-by: Miklos Vajna <redacted>
---
On Tue, Sep 25, 2007 at 04:13:06PM -0400, "J. Bruce Fields" [off-list ref] wrote:
quoted
One exception--the "series of tarballs" thing--I think it's cool that
you can just unpack a bunch of tarballs and string them together into a
git history. It gives a good sense of how git works, and I don't think
it's documented explicitly anywhere. I think that might be kinda fun to
write up. But I haven't tried.
something like this?
Neat-o, I'd missed (or forgotten about) import-tars.perl.
But I'd prefer to keep this first explanation of how to initialize and
commit to a new project pretty streamlined, and I don't think this is
really necessary here. So let's save this up until we have enough
material for a separate chapter or section on interacting with other
scm's.
--b.
@@ -978,6 +978,19 @@ $ git add . # include everything below ./ in the first commit: $ git commit -------------------------------------------------+If you already have a series of tarballs (typically previous releases without+using a version control system):++-------------------------------------------------+$ mkdir project+$ cd project+$ git init+$ perl import-tars.perl /path/to/tarballs/*.tar.bz2+$ git checkout import-tars+-------------------------------------------------++You can find `import-tars.perl` in the `contrib/fast-import/` directory.+ [[how-to-make-a-commit]] How to make a commit --------------------
On Wed, Sep 26, 2007 at 02:14:51PM -0400, "J. Bruce Fields" [off-list ref] wrote:
Neat-o, I'd missed (or forgotten about) import-tars.perl.
But I'd prefer to keep this first explanation of how to initialize and
commit to a new project pretty streamlined, and I don't think this is
really necessary here. So let's save this up until we have enough
material for a separate chapter or section on interacting with other
scm's.
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:43:36
Hi,
On Wed, 26 Sep 2007, J. Bruce Fields wrote:
On Wed, Sep 26, 2007 at 12:37:04AM +0200, Miklos Vajna wrote:
quoted
Signed-off-by: Miklos Vajna <redacted>
---
On Tue, Sep 25, 2007 at 04:13:06PM -0400, "J. Bruce Fields" [off-list ref] wrote:
quoted
One exception--the "series of tarballs" thing--I think it's cool that
you can just unpack a bunch of tarballs and string them together into a
git history. It gives a good sense of how git works, and I don't think
it's documented explicitly anywhere. I think that might be kinda fun to
write up. But I haven't tried.
You should also mention
$ mkdir my-new-repo
$ cd my-new-repo
$ git init
$ for z in /blub/*.zip
do
rm -rf * 2> /dev/null &&
unzip "$z" &&
git add . &&
git commit -m "$z" ||
break
done
import-tars.pl is much faster than this, of course, when it comes to tars,
but it has no clue about other archive formats.
Ciao,
Dscho
From: J. Bruce Fields <hidden> Date: 2016-06-15 22:43:36
On Wed, Sep 26, 2007 at 08:22:04PM +0200, Miklos Vajna wrote:
On Wed, Sep 26, 2007 at 02:14:51PM -0400, "J. Bruce Fields" [off-list ref] wrote:
quoted
Neat-o, I'd missed (or forgotten about) import-tars.perl.
But I'd prefer to keep this first explanation of how to initialize and
commit to a new project pretty streamlined, and I don't think this is
really necessary here. So let's save this up until we have enough
material for a separate chapter or section on interacting with other
scm's.
okay, now it's saved by gmane :)
Also in my git tree--I took yours and Johannes' suggestions, put them in
a blender, and added a brief skeleton of a new chapter at:
git://linux-nfs.org/~bfields/git.git docwork-foreign-scms
--b.