contributors in having a
read-only GIT mirror? The complaints I've seen so far are mostly in the
other direction (i.e., committing or applying patches). I'm not talking
about generic advantages of GIT: everybody here can be assumed to have a
good working knowledge of both SVN and GIT. What concret
gt;>>>>>
>>>>>>>
>>>>>>>
>>>>>>> @herbert, if nobody objects will you reopen the ticket, or should I
?
>>>>>>
>>>>>>
>>>>>>
>>>>>> I have reopened the JIRA issue and requ
reopen the ticket, or should I ?
I have reopened the JIRA issue and requested a read-only mirror for now.
And what would be the advantage for real contributors in having a
read-only
GIT mirror? The complaints I've seen so far are mostly in the other
direction (i.e., committing or app
>>>>
> >>>> I have reopened the JIRA issue and requested a read-only mirror for
> now.
> >>>
> >>>
> >>>
> >>> And what would be the advantage for real contributors in having a
> >>> read-only
> >>> GIT
6:48, janI wrote:
>>>>>
>>>>>
>>>>> @herbert, if nobody objects will you reopen the ticket, or should I ?
>>>>
>>>>
>>>> I have reopened the JIRA issue and requested a read-only mirror for now.
>>>
>>>
&g
for now.
And what would be the advantage for real contributors in having a read-only
GIT mirror? The complaints I've seen so far are mostly in the other
direction (i.e., committing or applying patches). I'm not talking about
generic advantages of GIT: everybody here can be assumed to h
issue and requested a read-only mirror for now.
And what would be the advantage for real contributors in having a
read-only
GIT mirror? The complaints I've seen so far are mostly in the other
direction (i.e., committing or applying patches). I'm not talking about
generic advanta
or should I ?
> >>
> >> I have reopened the JIRA issue and requested a read-only mirror for now.
> >
> >
> > And what would be the advantage for real contributors in having a
> read-only
> > GIT mirror? The complaints I've seen so far are mos
ead-only mirror for now.
>
>
> And what would be the advantage for real contributors in having a read-only
> GIT mirror? The complaints I've seen so far are mostly in the other
> direction (i.e., committing or applying patches). I'm not talking about
> generic advantages of
Herbert Duerr wrote:
On 12.11.2013 16:48, janI wrote:
@herbert, if nobody objects will you reopen the ticket, or should I ?
I have reopened the JIRA issue and requested a read-only mirror for now.
And what would be the advantage for real contributors in having a
read-only GIT mirror? The
On 11/12/13 5:37 PM, janI wrote:
> On 12 November 2013 17:32, Jürgen Schmidt wrote:
>
>> On 11/12/13 5:24 PM, janI wrote:
>>> On 12 November 2013 17:18, Jürgen Schmidt wrote:
>>>
On 11/12/13 5:06 PM, Herbert Duerr wrote:
> On 12.11.2013 16:48, janI wrote:
>> based on the discussion
On 12 November 2013 17:32, Jürgen Schmidt wrote:
> On 11/12/13 5:24 PM, janI wrote:
> > On 12 November 2013 17:18, Jürgen Schmidt wrote:
> >
> >> On 11/12/13 5:06 PM, Herbert Duerr wrote:
> >>> On 12.11.2013 16:48, janI wrote:
> based on the discussion in thread "XML files are binary" and h
On 11/12/13 5:24 PM, janI wrote:
> On 12 November 2013 17:18, Jürgen Schmidt wrote:
>
>> On 11/12/13 5:06 PM, Herbert Duerr wrote:
>>> On 12.11.2013 16:48, janI wrote:
based on the discussion in thread "XML files are binary" and herberts
comments I had a chat with jfarrell (the infra gi
iled.
But you don't have to work like that. Instead of creating branches
(which still works well for little changes, eg test changes of one file
on its own branch) you can create clones. That is how I currently
work. I have one local git mirror of our svn repository and a couple of
clone
On 12 November 2013 17:18, Jürgen Schmidt wrote:
> On 11/12/13 5:06 PM, Herbert Duerr wrote:
> > On 12.11.2013 16:48, janI wrote:
> >> based on the discussion in thread "XML files are binary" and herberts
> >> comments I had a chat with jfarrell (the infra git specialist).
> >>
> >> We can have a
On 11/12/13 5:06 PM, Herbert Duerr wrote:
> On 12.11.2013 16:48, janI wrote:
>> based on the discussion in thread "XML files are binary" and herberts
>> comments I had a chat with jfarrell (the infra git specialist).
>>
>> We can have a GIT Read/Only mirror very easy (standard)
>>
>> We cannot have
On 11/12/13 5:02 PM, Rob Weir wrote:
> On Tue, Nov 12, 2013 at 10:57 AM, Jürgen Schmidt
> wrote:
>> On 11/12/13 4:48 PM, janI wrote:
>>> Hi.
>>>
>>> based on the discussion in thread "XML files are binary" and herberts
>>> comments I had a chat with jfarrell (the infra git specialist).
>>>
>>> We
On 12 November 2013 16:57, Jürgen Schmidt wrote:
> On 11/12/13 4:48 PM, janI wrote:
> > Hi.
> >
> > based on the discussion in thread "XML files are binary" and herberts
> > comments I had a chat with jfarrell (the infra git specialist).
> >
> > We can have a GIT Read/Only mirror very easy (stand
On 12 November 2013 17:02, Rob Weir wrote:
> On Tue, Nov 12, 2013 at 10:57 AM, Jürgen Schmidt
> wrote:
> > On 11/12/13 4:48 PM, janI wrote:
> >> Hi.
> >>
> >> based on the discussion in thread "XML files are binary" and herberts
> >> comments I had a chat with jfarrell (the infra git specialist)
On 12.11.2013 16:48, janI wrote:
based on the discussion in thread "XML files are binary" and herberts
comments I had a chat with jfarrell (the infra git specialist).
We can have a GIT Read/Only mirror very easy (standard)
We cannot have a GIT Read/write mirror (restriction from infra)
We can
On Tue, Nov 12, 2013 at 10:57 AM, Jürgen Schmidt wrote:
> On 11/12/13 4:48 PM, janI wrote:
>> Hi.
>>
>> based on the discussion in thread "XML files are binary" and herberts
>> comments I had a chat with jfarrell (the infra git specialist).
>>
>> We can have a GIT Read/Only mirror very easy (stand
On 11/12/13 4:48 PM, janI wrote:
> Hi.
>
> based on the discussion in thread "XML files are binary" and herberts
> comments I had a chat with jfarrell (the infra git specialist).
>
> We can have a GIT Read/Only mirror very easy (standard)
>
> We cannot have a GIT Read/write mirror (restriction f
Hi.
based on the discussion in thread "XML files are binary" and herberts
comments I had a chat with jfarrell (the infra git specialist).
We can have a GIT Read/Only mirror very easy (standard)
We cannot have a GIT Read/write mirror (restriction from infra)
We can switch completely to GIT (whic
immediate benefit of being a stable
reference: As SVN allows editing properties of older commits individual
imports of the codebase via git-svn are different and result in
unpredictable commit-ids which prevents an efficient DVCS working style.
An official git-mirror of our SVN sub-tree would solve
Hi.
We have INFRA 5590 pending. When I (and infra) reads it, its only a request
for a RO mirror.
I understood from another discussion, that we wanted to be able to do git
commit, that automatically updated the svn (orignial) repository.
I my understanding is correct the ticket should be updated
On 02.12.2012 11:17, Andrea Pescetti wrote:
On 30/11/2012 Herbert Duerr wrote:
It would all be much simpler if we had an official git-mirror [1] of our
svn-repository.
OK, this will also make contributing easier for the new developers who
know only git, since they will be able to checkout
On 30/11/2012 Herbert Duerr wrote:
It would all be much simpler if we had an official git-mirror [1] of our
svn-repository.
OK, this will also make contributing easier for the new developers who
know only git, since they will be able to checkout (clone) only trunk,
branches and tags and
istory. I really don't want to go back to use svn directly.
It would all be much simpler if we had an official git-mirror [1] of
our svn-repository. Before filing an issue for this I'd like to get
consensus on that, even if only lazy consensus.
[1] http://www.apache.org/dev/git
For t
back to use svn directly.
It would all be much simpler if we had an official git-mirror [1] of our
svn-repository. Before filing an issue for this I'd like to get
consensus on that, even if only lazy consensus.
[1] http://www.apache.org/dev/git
For the requested infos I suggest:
- Name of t
29 matches
Mail list logo
