From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Daniele Segato <daniele.bilug@gmail.com>
Cc: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Locally manage user/branch setting files without pushing them remotely
Date: Thu, 12 Nov 2009 12:15:30 +0100 [thread overview]
Message-ID: <20091112111530.GC25398@vidovic> (raw)
In-Reply-To: <9accb4400911120213w35efcad3q8a24d99c37a5e8c5@mail.gmail.com>
The 12/11/09, Daniele Segato wrote:
>
> > I think you should look at 'git subtree' or 'git submodule' to track the
> > setting files out of the _main_ repository and _inside_ the main
> > development directory.
>
> will they work with git-svn?
> I'm not very familiar with them anyway.
Not the way you'd like to, I think. This could mean having as many svn
repo as git subtree/submodule.
> May be using an external/local repository for those files.
> but then I would like to have a way to link them automatically.
>
> may be this can be achieved with some hook script..
You could look at 'man githooks'.
> What I have in mind is something like this:
>
> 1. creating a local repo "confrepo" on the same directory where I have
> the real repo
> 2. .gitignore for all my local config file in the real repo
> 3. using the confrepo to store my local scripts and replicate in it
> the same branch structure of my real repo
>
> 4. may be then I can create some hook script that when I do
>
> $ git checkout experimental
>
> a) it try to do the same on the confrepo (checkout experimental), if
> the branch doesn't exist it does nothing else
> b) copy everythink in the confrepo to my realrepo (overwriting if needed)
>
>
> that way I could have something automatic. The only think I couldn't
> have is, looking back in history, a way to know which config was in
> place for an old commit.
>
>
> could you tell me if this is even possible?
I think, yes.
> I'm going a little off-topic here proposing an idea for a new feature
> What about adding a git feature to "link" different git repository?
> Or providing a way to have 2 (or more) git repository in the same working area.
Patches are welcome. That said, I guess it won't be needed. As you
pointed out, the flexibility has been implemented in the hooks system.
Consequently, we all have to write the appropriate scripts. But OTOH, it
is more flexible than any feature matching _one_ workflow.
--
Nicolas Sebrecht
prev parent reply other threads:[~2009-11-12 11:15 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
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 [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=20091112111530.GC25398@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=daniele.bilug@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).