SRY: The question is in fact not to let people to perform these steps
manually.
вторник, 10 июня 2014 г., 14:09:57 UTC+3 пользователь Alexander Zorgiev
написал:
>
> The question is in fact not to let people not to perform these steps
> manually.
>
> вторник, 3 июня 2014 г., 15:32:26 UTC+3 польз
It seems there is no comfortable platform-independed way to do this. Maybe
feature request?
вторник, 3 июня 2014 г., 15:34:12 UTC+3 пользователь John McKown написал:
>
> On Tue, Jun 3, 2014 at 7:12 AM, Magnus Therning > wrote:
>
>> On Tue, Jun 03, 2014 at 04:24:43AM -0700, Pierre-François CLEMEN
Post-merge hook? Anyways someone needs to set up this post-merge hook in a
manual fashion.
вторник, 3 июня 2014 г., 15:34:12 UTC+3 пользователь John McKown написал:
>
> On Tue, Jun 3, 2014 at 7:12 AM, Magnus Therning > wrote:
>
>> On Tue, Jun 03, 2014 at 04:24:43AM -0700, Pierre-François CLEMENT
The question is in fact not to let people not to perform these steps
manually.
вторник, 3 июня 2014 г., 15:32:26 UTC+3 пользователь Pierre-François
CLEMENT написал:
>
> Sounds good enough. You could probably even embed it into a Makefile or a
> Gruntfile or whatever-file you're using if you alr
Symlinks has nothing to do with the fact that I want the part of the
configuration to be versioned. BTW on windows symlinks work kinda
differently. Of course since Vista/Server 2008 we have mklink bundled, but
I don't think msys.win will handle this situation correctly. Nevertheless
the fact th
For instance I want to put some git extensions into my project git
repository. The documentation states that the path must be accessible
through git --ext-path. This can be altered either globally or
per-repository basis in .config. But this file seems to be unversioned. If
we in future will ha
On Tue, Jun 03, 2014 at 07:34:10AM -0500, John McKown wrote:
> On Tue, Jun 3, 2014 at 7:12 AM, Magnus Therning wrote:
>
> > On Tue, Jun 03, 2014 at 04:24:43AM -0700, Pierre-François CLEMENT wrote:
> > >
> > >
> > > > I want to extend git commands set on per-repository basis and
> > therefore I
>
On Tue, Jun 3, 2014 at 7:12 AM, Magnus Therning wrote:
> On Tue, Jun 03, 2014 at 04:24:43AM -0700, Pierre-François CLEMENT wrote:
> >
> >
> > > I want to extend git commands set on per-repository basis and
> therefore I
> > > need to have VERSIONED sort of .config file
> > >
> >
> > You can use t
Sounds good enough. You could probably even embed it into a Makefile or a
Gruntfile or whatever-file you're using if you already have one. And about
the two-steps thing, you might want to get them to use a post-merge hook to
automate it.
--
You received this message because you are subscribed
On Tue, Jun 03, 2014 at 04:24:43AM -0700, Pierre-François CLEMENT wrote:
>
>
> > I want to extend git commands set on per-repository basis and therefore I
> > need to have VERSIONED sort of .config file
> >
>
> You can use the repository's .git/config file to set repo-specific
> configuration,
> I want to extend git commands set on per-repository basis and therefore I
> need to have VERSIONED sort of .config file
>
You can use the repository's .git/config file to set repo-specific
configuration, but why would you want it to be versioned in the project
itself? It'd force anybody who
On Monday, June 2, 2014 3:07:18 PM UTC+2, Alexander Zorgiev wrote:
>
> Hello everybody,
>
> I wonder if there is such a thing. For instance I want to extend git
> commands set on per-repository basis and therefore I need to have VERSIONED
> sort of .config file where I can put some command there
12 matches
Mail list logo
