git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Andrew <nick@nick-andrew.net>
To: "Łukasz Lew" <lukasz.lew@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to maintain private/secret/confidential branch.
Date: Mon, 15 Dec 2008 01:55:18 +1100	[thread overview]
Message-ID: <20081214145518.GA26380@mail.local.tull.net> (raw)
In-Reply-To: <c55009e70812140549t6547c1d6jf7780f91b5074e73@mail.gmail.com>

On Sun, Dec 14, 2008 at 02:49:50PM +0100, Łukasz Lew wrote:
> I don't know how to make such a scenario work:
> - two repositories: pub, priv
> - priv is clone/branch of pub
> - there is some constant developement both in pub and priv
> - there are regular syncs with pub in priv
> 
> Problem:
> Occasionally I want to push some changes from priv to pub.
> Then after syncing with pub I want to get as few conflicts as possible.
> 
> Is it possible to do with git?

Git can do almost anything. One should instead ask "How to do this
with git?" :-)

If I understand your problem, you could solve it with git cherry-pick
and rebase. On priv, make a for-public branch from a pub branch. Then
cherry-pick the commits you want from your private branch into the
for-public branch. Push your for-public branch to pub, then rebase
your private branch.

Nick.

  reply	other threads:[~2008-12-14 14:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14 13:49 How to maintain private/secret/confidential branch Łukasz Lew
2008-12-14 14:55 ` Nick Andrew [this message]
2008-12-14 15:38   ` Łukasz Lew
2008-12-14 16:06     ` Alexander Potashev
2008-12-14 16:48       ` Łukasz Lew
2008-12-15 20:31         ` Daniel Barkalow
2008-12-17 19:57           ` Łukasz Lew
2008-12-17 20:27             ` Daniel Barkalow
2008-12-17 22:31               ` Łukasz Lew
2008-12-18  8:03                 ` Daniel Barkalow
2008-12-14 16:13     ` Sitaram Chamarty

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=20081214145518.GA26380@mail.local.tull.net \
    --to=nick@nick-andrew.net \
    --cc=git@vger.kernel.org \
    --cc=lukasz.lew@gmail.com \
    /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).