From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: Daniele Segato <daniele.bilug@gmail.com>
Cc: Yann Simon <yann.simon.fr@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Locally manage user/branch setting files without pushing them remotely
Date: Wed, 11 Nov 2009 14:46:43 +0100 [thread overview]
Message-ID: <4d8e3fd30911110546m1a5012f2g99f2d0c7ca829876@mail.gmail.com> (raw)
In-Reply-To: <9accb4400911110500y37437dc5h16388b07a734dc6d@mail.gmail.com>
On Wed, Nov 11, 2009 at 2:00 PM, Daniele Segato <daniele.bilug@gmail.com> wrote:
> On Wed, Nov 11, 2009 at 1:14 PM, Yann Simon <yann.simon.fr@gmail.com> wrote:
>> I am in the same situation.
>> What I did is not to add these files to .gitignore.
>> On my "work" branch, I commited these files in a separate commit
>> "local changes".
>> When I want to push to svn, I switch to the branch "master", and
>> cherry-pick the commit I want to push.
>> $ git checkout master
>> $ git svn rebase
>> $ git cherry-pick work
>> $ git svn dcommit
>> $ git checkout work
>> $ git rebase master
>>
>> This workflow could maybe be better. Suggestions welcome.
>
> hum
> but I don't want to push those files
If you follow Yann's advise you won't push to the svn repo the "private" files,
they will be /only/ stored in you local repo.
The cons of that approach is that you will have to cherrypick all the
commits you want to push to the svn repo from the "working branch" to
the master branch.
Ciao,
--
Paolo
next prev parent reply other threads:[~2009-11-11 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 12:01 Locally manage user/branch setting files without pushing them remotely Daniele Segato
2009-11-11 12:14 ` Yann Simon
2009-11-11 13:00 ` Daniele Segato
2009-11-11 13:06 ` Yann Simon
2009-11-11 13:46 ` Paolo Ciarrocchi [this message]
2009-11-11 19:24 ` Nicolas Sebrecht
[not found] ` <9accb4400911120118t3257a1n6f2a05abb1008c8@mail.gmail.com>
2009-11-12 9:29 ` Daniele Segato
2009-11-12 9:31 ` Nicolas Sebrecht
2009-11-12 10:13 ` Daniele Segato
2009-11-12 11:15 ` Nicolas Sebrecht
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=4d8e3fd30911110546m1a5012f2g99f2d0c7ca829876@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=daniele.bilug@gmail.com \
--cc=git@vger.kernel.org \
--cc=yann.simon.fr@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).