On Thu, Jun 6, 2013 at 3:42 PM, benoît person wrote:
> From what I know, git does not support branch permissions. The best
> way to deal with that kind of permissions-thingy is to create two
> repos : a main repo and a fork for your new developer. He would only
> have permissions to pull from the
On Thu, Jun 6, 2013 at 6:39 PM, robe070 wrote:
> One of the issues with our source code is that there is one file that is
> critical to our development. If its changed in our working directory then
> the entire solution needs to be re-built. We currently avoid this and
> usually end up needing to
Hi,
I am sorry yes I am using UBUNTU and here is my system configuration
No LSB modules are available.
Distributor ID:Ubuntu
Description:Ubuntu 10.04.4 LTS
Release:10.04
Codename:lucid
Please help.
--
You received this message because you are subscribed to the Google Group
Its not about splitting the push that another developer has submitted. Its
not about splitting file A and CRIT.
Its about not needing any part of that commit in order to work in our
current environment. With Git you are forced to pull both A and CRIT before
pushing your changes. I don't want ei
On 10 June 2013 03:09, robe070 wrote:
> Different branches or submodule won't work. The change to A and CRIT will be
> required soon - but at the request of the receiver, not forced upon you by
> Git.
You are not forced to pull / push to all branches you know ? You could
always pull / push in the
On Sun, Jun 9, 2013 at 6:39 PM, benoît person wrote:
> On 10 June 2013 03:09, robe070 wrote:
>> Different branches or submodule won't work. The change to A and CRIT will be
>> required soon - but at the request of the receiver, not forced upon you by
>> Git.
>
> You are not forced to pull / push
Thats definitely food for thought. I could imagine a branch thats for
maintaining CRIT, which may be the main Development branch or you merge to
Development as and when you are complete, with CRIT. Otherwise changes are
made to Feature branches. Those Feature branches could be merged as desired
On Sun, Jun 9, 2013 at 7:43 PM, robe070 wrote:
> Whats an 'fs clone'?
sorry, real name is git clone --local, it does hardlinks by default so
doesn't copy anything.
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from thi
> $ time git repack -d -l -f --depth=250 --window=250 -A --window-memory=1g
>From the manual pages and testing its behavior, when "git repack" is
executed by "git gc", the default --window-memory value is supplied by
the pack.windowMemory configuration value:
pack.windowMemory
We're pretty much stuck with subversion over here, yet a few colleagues
would like to try Git.
The Git-Book has a note that it might make sense to create a git-svn clone
and have others git clone that one - too bad it doesn't explain how (altho
one could think the obvious).
There are tutorials
On 10 June 2013 02:31, Deepak Selvaraj wrote:
> Hi,
>
> I am sorry yes I am using UBUNTU and here is my system configuration
>
> No LSB modules are available.
> Distributor ID:Ubuntu
> Description:Ubuntu 10.04.4 LTS
Desktop 10.04 ran out of support 2013-05-09 so that is probably the reaso
11 matches
Mail list logo
