On 05/11/2014 11:34 PM, Junio C Hamano wrote:
Sitaram Chamarty writes:
But what I was looking for was validation from git.git folks of the idea
of replicating what "git clone -l" does, for an *existing* repo.
For example, I'm assuming that bringing in only the objects -- without
any of the re
Sitaram Chamarty writes:
> But what I was looking for was validation from git.git folks of the idea
> of replicating what "git clone -l" does, for an *existing* repo.
>
> For example, I'm assuming that bringing in only the objects -- without
> any of the refs pointing to them, making them all dan
On 05/11/2014 08:41 AM, Storm-Olsen, Marius wrote:
On 5/10/2014 9:10 PM, Sitaram Chamarty wrote:
1. Clone remote repo
2. Hack hack hack
3. Fork repo on server
4. Push changes to your own remote repo
is equally efficient.
Your suggestions are good for a manual setup where
On 5/10/2014 9:10 PM, Sitaram Chamarty wrote:
> On 05/11/2014 07:04 AM, Storm-Olsen, Marius wrote:
>> On 5/10/2014 8:04 PM, Sitaram Chamarty wrote: Many of the Git repo
>> managers will neatly set up a server-side repo clone for you, with
>> alternates into the original repo saving both network and
On 05/11/2014 07:04 AM, Storm-Olsen, Marius wrote:
On 5/10/2014 8:04 PM, Sitaram Chamarty wrote:
On 05/11/2014 02:32 AM, Junio C Hamano wrote: That's an interesting
thread and it's recent too. However, it's about clone (though the
intro email mentions other commands also).
I'm specifically int
On 5/10/2014 8:04 PM, Sitaram Chamarty wrote:
> On 05/11/2014 02:32 AM, Junio C Hamano wrote: That's an interesting
> thread and it's recent too. However, it's about clone (though the
> intro email mentions other commands also).
>
> I'm specifically interested in push efficiency right now. When y
On 05/11/2014 02:32 AM, Junio C Hamano wrote:
Sitaram Chamarty writes:
Is there a trick to optimising a push by telling the receiver to pick up
missing objects from some other repo on its own server, to cut down even
more on network traffic?
So, hypothetically,
git push user@host:repo1
Sitaram Chamarty writes:
> Is there a trick to optimising a push by telling the receiver to pick up
> missing objects from some other repo on its own server, to cut down even
> more on network traffic?
>
> So, hypothetically,
>
> git push user@host:repo1 --look-for-objects-in=repo2
>
> I'm aw
On Sat, May 10, 2014 at 10:32:26AM -0700, milki wrote:
> On 17:23 Sat 10 May , brian m. carlson wrote:
> > I don't believe this is possible. There has been some discussion on
> > related matters at least fairly recently, though.
> >
> > Part of the reason nobody has implemented this is becaus
On 17:23 Sat 10 May , brian m. carlson wrote:
> I don't believe this is possible. There has been some discussion on
> related matters at least fairly recently, though.
>
> Part of the reason nobody has implemented this is because it exposes
> additional security concerns. If I create a commi
On Sat, May 10, 2014 at 07:09:37PM +0530, Sitaram Chamarty wrote:
> Hi,
>
> Is there a trick to optimising a push by telling the receiver to pick up
> missing objects from some other repo on its own server, to cut down even
> more on network traffic?
>
> So, hypothetically,
>
> git push user
On Sat, May 10, 2014 at 8:39 PM, Sitaram Chamarty wrote:
> Hi,
>
> Is there a trick to optimising a push by telling the receiver to pick up
> missing objects from some other repo on its own server, to cut down even
> more on network traffic?
>
> So, hypothetically,
>
> git push user@host:repo1
Hi,
Is there a trick to optimising a push by telling the receiver to pick up
missing objects from some other repo on its own server, to cut down even
more on network traffic?
So, hypothetically,
git push user@host:repo1 --look-for-objects-in=repo2
I'm aware of the alternates mechanism, but
13 matches
Mail list logo
