On Wed, Oct 28, 2015 at 4:16 AM, Branko Čibej wrote:
> On 28.10.2015 04:39, Nico Kadel-Garcia wrote:
>> On Tue, Oct 27, 2015 at 12:07 PM, Branko Čibej wrote:
>>> On 27.10.2015 14:33, Nico Kadel-Garcia wrote:
See above. It sounds like you need to talk to Github about making an
exception
On 28.10.2015 04:39, Nico Kadel-Garcia wrote:
> On Tue, Oct 27, 2015 at 12:07 PM, Branko Čibej wrote:
>> On 27.10.2015 14:33, Nico Kadel-Garcia wrote:
>>> See above. It sounds like you need to talk to Github about making an
>>> exception to their default settings for revision 0. A freshly
>>> init
On Tue, Oct 27, 2015 at 12:07 PM, Branko Čibej wrote:
> On 27.10.2015 14:33, Nico Kadel-Garcia wrote:
>> See above. It sounds like you need to talk to Github about making an
>> exception to their default settings for revision 0. A freshly
>> initialized git repo, with no files or property changes
Branko Čibej writes:
> Subversion has required a valid,
> non-empty svn:date on every revision since before 1.0.
Subversion also allows revisions without an svn:date. It is possible to
delete svn:date and it is possible for path-based authz to make the date
invisible. svnsync will cope with th
On 27.10.2015 15:18, Fredrik Orderud wrote:
> Thanks for the tips Nico.
>
> I am well aware that git-svn sync can be troublesome and best avoided if
> possible. The planned syncing will be one-way, against a read-only svn
> mirror repo maintained for "corporate policy" reasons.
>
> GitHub have alre
On 27.10.2015 14:33, Nico Kadel-Garcia wrote:
> See above. It sounds like you need to talk to Github about making an
> exception to their default settings for revision 0. A freshly
> initialized git repo, with no files or property changes submitted, has
> *no* valid logs, and "git log" fails with a
Thanks for the tips Nico.
I am well aware that git-svn sync can be troublesome and best avoided if
possible. The planned syncing will be one-way, against a read-only svn
mirror repo maintained for "corporate policy" reasons.
GitHub have already been contacted regarding the issue, but I thought it
On Tue, Oct 27, 2015 at 9:03 AM, Fredrik Orderud wrote:
> I'm experiencing problems using svnsync to mirror a GitHub repo.
>
> GitHub exposes a SVN API, that enables SVN clients to work against the
> underlying GIT repo
> (https://help.github.com/articles/support-for-subversion-clients/). This
> m
I'm experiencing problems using svnsync to mirror a GitHub repo.
GitHub exposes a SVN API, that enables SVN clients to work against the
underlying GIT repo (
https://help.github.com/articles/support-for-subversion-clients/). This
mostly works great, but I'm struggling to combine it with synsync.
