git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: how to combine two clones in a collection
Date: Wed, 11 Jul 2007 12:46:39 +0200	[thread overview]
Message-ID: <f72ceh$ke6$1@sea.gmane.org> (raw)
In-Reply-To: 20070710174543.GA16054@piper.oerlikon.madduck.net

martin f krafft wrote:

> I wonder how to create a project with two completely independent
> branches which have no common ancestry. I don't think it's possible.
> One needs a throwaway branch to create the first commit, then branch
> each of the two branches off that, then delete the throwaya branch
> (or keep it around).

Git repository itself  has a few completely independent branches, some of
them visible. One of them, the 'todo' branch is actually from independent
repository, two other, 'man' and 'html' are generated automatically by the
build script.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

      parent reply	other threads:[~2007-07-11 10:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 22:22 how to combine two clones in a collection martin f krafft
2007-07-10  2:35 ` Linus Torvalds
2007-07-10  6:21   ` martin f krafft
2007-07-10  7:17     ` Junio C Hamano
2007-07-10  7:40       ` martin f krafft
2007-07-10  7:51     ` Martin Langhoff
2007-07-10 17:05     ` Linus Torvalds
2007-07-10 17:45       ` martin f krafft
2007-07-10 18:27         ` Brian Gernhardt
2007-07-10 19:27           ` Kalle Pokki
2007-07-10 20:00             ` Brian Gernhardt
2007-07-10 23:45               ` Robin Rosenberg
2007-07-11 18:13                 ` martin f krafft
2007-07-11 18:37                   ` Johannes Schindelin
2007-07-11 19:22                     ` martin f krafft
2007-07-11 10:46         ` Jakub Narebski [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='f72ceh$ke6$1@sea.gmane.org' \
    --to=jnareb@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 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).