Re: [webkit-dev] Github mirror is not updating

[Jonathan Bedard via webkit-dev]

Not at first, but at the moment, yes, it is intentional. We are working on 
migrating WebKit to a more permanent and complete Git repository, which 
involves editing history. Because of this, we didn’t want to further the 
confusion we already have with two different sets of git hashes. The new 
repository should be pushed in the next week or two

In the mean time, https://git.webkit.org/WebKit-https.git 
 (secure, but different hashes than 
GitHub) and https://git.webkit.org/WebKit.git 
 (uses the same hashes as GitHub), are 
up-to-date mirrors.

Jonathan

> Hi,
> 
> I noticed that the github mirror at https://github.com/webkit/webkit is not 
> getting
> the latest commits from WebKit (it is now about a month behind). Is that 
> intentional?
> 
> Thanks,
> -- 
> Adrien / PulkoMandy
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Github mirror is not updating

[Ryosuke Niwa via webkit-dev]

On Thu, Nov 26, 2020 at 11:33 PM Adrien Destugues via webkit-dev <
webkit-dev@lists.webkit.org> wrote:

>
> I noticed that the github mirror at https://github.com/webkit/webkit is
> not getting
> the latest commits from WebKit (it is now about a month behind). Is that
> intentional?
>

We're actively working on resolving this issue. This current disruption is
caused by GitHub repository preferring to Git repository created off of
accessing the source-of-the-truth subversion repository over HTTPS instead
of accessing it over HTTP. However, since we're in the midst of Git
transition and this transition requires us adding a new numeric
identifier to each commit message, we're doing that work so that we can
push one new Git repository to GitHub instead of temporarily fixing this
issue and then later causing a disruption again. Sorry for the
inconveniences & thanks for your understanding.

- R. Niwa
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

[webkit-dev] Github mirror is not updating

[Adrien Destugues via webkit-dev]

Hi,

I noticed that the github mirror at https://github.com/webkit/webkit is not 
getting
the latest commits from WebKit (it is now about a month behind). Is that 
intentional?

Thanks,
-- 
Adrien / PulkoMandy

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] github mirror

[Adam Barth]

On Mon, Aug 6, 2012 at 4:59 AM, KwangYul Seo  wrote:
> What's the current status? Do they still have different hashes?

Yes.

> I am trying to push a few commits to my GitHub WebKit repo from my repo
> cloned from git.webkit.org. It seems I am pushing the entire repo :(

Correct.  That's not going to work well.  Instead you should fork
https://github.com/WebKit/webkit and rebase your changes onto your
fork.

Adam


> On Mon, Apr 30, 2012 at 2:48 AM, Adam Barth  wrote:
>>
>> Tor,
>>
>> I think we should retire the author rewriting script on GitHub.
>>
>> Jame's is right that there's a lot of value in having git.webkit.org
>> and GitHub using the same hashes.  For example, both Eric and Gavin
>> requested that when they started using GitHub.
>>
>> We would have some trouble adopting the author rewriting script on
>> git.webkit.org.  For example, the instructions for using git with
>> WebKit  suggest
>> configuring git-svn to allow you to commit from your git repository.
>> When git-svn imports changes from SVN into your git repository, it
>> won't know to apply the author rewriting script.  That will cause your
>> local repository to diverge from an author-rewriting git.webkit.org,
>> which is bad times.
>>
>> Therefore, it seems like the best way to synchronize the hashes
>> between git.webkit.org and GitHub is to retire the author rewriting
>> script on GitHub and do a non-fastforward push of the unrewritten
>> repository.  That will be somewhat disruptive for folks currently
>> using the GitHub repository, but at least it's only a one-time cost.
>>
>> Adam
>>
>>
>> On Tue, Apr 24, 2012 at 11:06 AM, James Robinson 
>> wrote:
>> > On Tue, Apr 24, 2012 at 7:15 AM, Tor Arne Vestbø
>> > 
>> > wrote:
>> >> On 24.04.12 16:04, ext Shezan Baig wrote:
>> >>> On Tue, Apr 24, 2012 at 9:55 AM, Adam Roben  wrote:
>> > In what situation does this cause issues?
>> 
>> 
>>  Probably the biggest issue is for people who've been using
>>  git.webkit.org and now want to try out GitHub. Since the commits are
>>  distinct between the two repositories, they have to do a full clone
>>  to
>>  make the switch.
>> >>>
>> >>>
>> >>>
>> >>> In theory though, these users should be able to just add a remote to
>> >>> their existing clone.  Then it will just sync the commit objects, and
>> >>> not the trees and blobs.  Not ideal, they would have two different
>> >>> 'masters', but still doable, and not *that* much of an overhead.
>> >>> Switching between the different masters should also be fast since the
>> >>> trees will be the same.
>> >>
>> >>
>> >> Right, a fetch should ideally just pull down the commit objects, but it
>> >> appears git does not have this optimization. If it did, I don't think
>> >> the
>> >> issue of two remote masters would be that big, since you would at some
>> >> point
>> >> likely transition to use one of the mirrors anyways. And if not, having
>> >> multiple mirrors/remotes should be fine -- I'm using both the github
>> >> and
>> >> gitorious mirror without any issues.
>> >>
>> >>
>> >>> But I agree these two repos should probably merge sooner rather than
>> >>> later, just to avoid confusion for new users etc :)
>> >>
>> >>
>> >> I would support that if it means cleaning up the author-script (which
>> >> I'm
>> >> happy to do), and using that on webkit.org.
>> >
>> >
>> > Whatever we decide to do in the future, author rewriting seems like
>> > extremely low value compared to having matching SHA1s.  I think we
>> > should
>> > get a clone on github.com that matches the existing git.webkit.org SHA1s
>> > and
>> > then make sure that they stay in sync (either with rewriting or not, but
>> > whatever webkit.org does).
>> >
>> > - James
>> >
>> >>
>> >>
>> >> tor arne
>> >>
>> >>
>> >> ___
>> >> webkit-dev mailing list
>> >> webkit-dev@lists.webkit.org
>> >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>> >
>> >
>> >
>> > ___
>> > webkit-dev mailing list
>> > webkit-dev@lists.webkit.org
>> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>> >
>> ___
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] github mirror

[KwangYul Seo]

Hi, Adam.

What's the current status? Do they still have different hashes?

I am trying to push a few commits to my GitHub WebKit repo from my repo
cloned from git.webkit.org. It seems I am pushing the entire repo :(

Regards,
Kwang Yul Seo


On Mon, Apr 30, 2012 at 2:48 AM, Adam Barth  wrote:

> Tor,
>
> I think we should retire the author rewriting script on GitHub.
>
> Jame's is right that there's a lot of value in having git.webkit.org
> and GitHub using the same hashes.  For example, both Eric and Gavin
> requested that when they started using GitHub.
>
> We would have some trouble adopting the author rewriting script on
> git.webkit.org.  For example, the instructions for using git with
> WebKit  suggest
> configuring git-svn to allow you to commit from your git repository.
> When git-svn imports changes from SVN into your git repository, it
> won't know to apply the author rewriting script.  That will cause your
> local repository to diverge from an author-rewriting git.webkit.org,
> which is bad times.
>
> Therefore, it seems like the best way to synchronize the hashes
> between git.webkit.org and GitHub is to retire the author rewriting
> script on GitHub and do a non-fastforward push of the unrewritten
> repository.  That will be somewhat disruptive for folks currently
> using the GitHub repository, but at least it's only a one-time cost.
>
> Adam
>
>
> On Tue, Apr 24, 2012 at 11:06 AM, James Robinson 
> wrote:
> > On Tue, Apr 24, 2012 at 7:15 AM, Tor Arne Vestbø <
> tor.arne.ves...@nokia.com>
> > wrote:
> >> On 24.04.12 16:04, ext Shezan Baig wrote:
> >>> On Tue, Apr 24, 2012 at 9:55 AM, Adam Roben  wrote:
> > In what situation does this cause issues?
> 
> 
>  Probably the biggest issue is for people who've been using
>  git.webkit.org and now want to try out GitHub. Since the commits are
>  distinct between the two repositories, they have to do a full clone to
>  make the switch.
> >>>
> >>>
> >>>
> >>> In theory though, these users should be able to just add a remote to
> >>> their existing clone.  Then it will just sync the commit objects, and
> >>> not the trees and blobs.  Not ideal, they would have two different
> >>> 'masters', but still doable, and not *that* much of an overhead.
> >>> Switching between the different masters should also be fast since the
> >>> trees will be the same.
> >>
> >>
> >> Right, a fetch should ideally just pull down the commit objects, but it
> >> appears git does not have this optimization. If it did, I don't think
> the
> >> issue of two remote masters would be that big, since you would at some
> point
> >> likely transition to use one of the mirrors anyways. And if not, having
> >> multiple mirrors/remotes should be fine -- I'm using both the github and
> >> gitorious mirror without any issues.
> >>
> >>
> >>> But I agree these two repos should probably merge sooner rather than
> >>> later, just to avoid confusion for new users etc :)
> >>
> >>
> >> I would support that if it means cleaning up the author-script (which
> I'm
> >> happy to do), and using that on webkit.org.
> >
> >
> > Whatever we decide to do in the future, author rewriting seems like
> > extremely low value compared to having matching SHA1s.  I think we should
> > get a clone on github.com that matches the existing git.webkit.orgSHA1s and
> > then make sure that they stay in sync (either with rewriting or not, but
> > whatever webkit.org does).
> >
> > - James
> >
> >>
> >>
> >> tor arne
> >>
> >>
> >> ___
> >> webkit-dev mailing list
> >> webkit-dev@lists.webkit.org
> >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
> >
> >
> >
> > ___
> > webkit-dev mailing list
> > webkit-dev@lists.webkit.org
> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
> >
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] github mirror

[Adam Barth]

Tor,

I think we should retire the author rewriting script on GitHub.

Jame's is right that there's a lot of value in having git.webkit.org
and GitHub using the same hashes.  For example, both Eric and Gavin
requested that when they started using GitHub.

We would have some trouble adopting the author rewriting script on
git.webkit.org.  For example, the instructions for using git with
WebKit  suggest
configuring git-svn to allow you to commit from your git repository.
When git-svn imports changes from SVN into your git repository, it
won't know to apply the author rewriting script.  That will cause your
local repository to diverge from an author-rewriting git.webkit.org,
which is bad times.

Therefore, it seems like the best way to synchronize the hashes
between git.webkit.org and GitHub is to retire the author rewriting
script on GitHub and do a non-fastforward push of the unrewritten
repository.  That will be somewhat disruptive for folks currently
using the GitHub repository, but at least it's only a one-time cost.

Adam


On Tue, Apr 24, 2012 at 11:06 AM, James Robinson  wrote:
> On Tue, Apr 24, 2012 at 7:15 AM, Tor Arne Vestbø 
> wrote:
>> On 24.04.12 16:04, ext Shezan Baig wrote:
>>> On Tue, Apr 24, 2012 at 9:55 AM, Adam Roben  wrote:
> In what situation does this cause issues?


 Probably the biggest issue is for people who've been using
 git.webkit.org and now want to try out GitHub. Since the commits are
 distinct between the two repositories, they have to do a full clone to
 make the switch.
>>>
>>>
>>>
>>> In theory though, these users should be able to just add a remote to
>>> their existing clone.  Then it will just sync the commit objects, and
>>> not the trees and blobs.  Not ideal, they would have two different
>>> 'masters', but still doable, and not *that* much of an overhead.
>>> Switching between the different masters should also be fast since the
>>> trees will be the same.
>>
>>
>> Right, a fetch should ideally just pull down the commit objects, but it
>> appears git does not have this optimization. If it did, I don't think the
>> issue of two remote masters would be that big, since you would at some point
>> likely transition to use one of the mirrors anyways. And if not, having
>> multiple mirrors/remotes should be fine -- I'm using both the github and
>> gitorious mirror without any issues.
>>
>>
>>> But I agree these two repos should probably merge sooner rather than
>>> later, just to avoid confusion for new users etc :)
>>
>>
>> I would support that if it means cleaning up the author-script (which I'm
>> happy to do), and using that on webkit.org.
>
>
> Whatever we decide to do in the future, author rewriting seems like
> extremely low value compared to having matching SHA1s.  I think we should
> get a clone on github.com that matches the existing git.webkit.org SHA1s and
> then make sure that they stay in sync (either with rewriting or not, but
> whatever webkit.org does).
>
> - James
>
>>
>>
>> tor arne
>>
>>
>> ___
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[David Barr]

On Wed, Apr 25, 2012 at 12:49 AM, Simon Hausmann
 wrote:
> On Tuesday, April 24, 2012 03:59:47 PM Tor Arne Vestbø wrote:
>> On 24.04.12 15:55, ext Adam Roben wrote:
>> > Probably the biggest issue is for people who've been using
>> > git.webkit.org and now want to try out GitHub. Since the commits are
>> > distinct between the two repositories, they have to do a full clone to
>> > make the switch.
>>
>> Any idea why git is not smarter when pulling down the objects?
>
> I think it's to minimize the traffic in the git protocol. If you just compare
> git commits, you can calculate the delta relatively quickly with fewer
> roundtrips. If server and client start to negotiate on the git object level
> itself it's going to take months to figure out which objects the client has 
> and
> which ones are missing :)

A relevant fact is that you may avoid clients having to re-fetch all
trees and blobs if the mirror hosts both histories on different heads,
eg. refs/heads/master and refs/heads/github.

--
David Barr
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[James Robinson]

On Tue, Apr 24, 2012 at 7:15 AM, Tor Arne Vestbø
wrote:

> On 24.04.12 16:04, ext Shezan Baig wrote:
>
>> On Tue, Apr 24, 2012 at 9:55 AM, Adam Roben  wrote:
>>
>>> In what situation does this cause issues?

>>>
>>> Probably the biggest issue is for people who've been using
>>> git.webkit.org and now want to try out GitHub. Since the commits are
>>> distinct between the two repositories, they have to do a full clone to
>>> make the switch.
>>>
>>
>>
>> In theory though, these users should be able to just add a remote to
>> their existing clone.  Then it will just sync the commit objects, and
>> not the trees and blobs.  Not ideal, they would have two different
>> 'masters', but still doable, and not *that* much of an overhead.
>> Switching between the different masters should also be fast since the
>> trees will be the same.
>>
>
> Right, a fetch should ideally just pull down the commit objects, but it
> appears git does not have this optimization. If it did, I don't think the
> issue of two remote masters would be that big, since you would at some
> point likely transition to use one of the mirrors anyways. And if not,
> having multiple mirrors/remotes should be fine -- I'm using both the github
> and gitorious mirror without any issues.
>
>
>  But I agree these two repos should probably merge sooner rather than
>> later, just to avoid confusion for new users etc :)
>>
>
> I would support that if it means cleaning up the author-script (which I'm
> happy to do), and using that on webkit.org.


Whatever we decide to do in the future, author rewriting seems like
extremely low value compared to having matching SHA1s.  I think we should
get a clone on github.com that matches the existing git.webkit.org SHA1s
and then make sure that they stay in sync (either with rewriting or not,
but whatever webkit.org does).

- James


>
> tor arne
>
>
> __**_
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/**mailman/listinfo.cgi/webkit-**dev
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Evan Martin]

On Tue, Apr 24, 2012 at 7:04 AM, Shezan Baig  wrote:
>> Probably the biggest issue is for people who've been using
>> git.webkit.org and now want to try out GitHub. Since the commits are
>> distinct between the two repositories, they have to do a full clone to
>> make the switch.
>
> In theory though, these users should be able to just add a remote to
> their existing clone.  Then it will just sync the commit objects, and
> not the trees and blobs.  Not ideal, they would have two different
> 'masters', but still doable, and not *that* much of an overhead.
> Switching between the different masters should also be fast since the
> trees will be the same.
>
> But I agree these two repos should probably merge sooner rather than
> later, just to avoid confusion for new users etc :)

People who have existing branches can use git grafts to manually merge
the "same" commit in the old and new branches.  Then tools like "git
merge" of the master of the new branch will do the right thing
implicitly.

(http://evan-tech.livejournal.com/255341.html is an old post about
doing a similar sort of thing)
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Simon Hausmann]

On Tuesday, April 24, 2012 03:59:47 PM Tor Arne Vestbø wrote:
> On 24.04.12 15:55, ext Adam Roben wrote:
> > Probably the biggest issue is for people who've been using
> > git.webkit.org and now want to try out GitHub. Since the commits are
> > distinct between the two repositories, they have to do a full clone to
> > make the switch.
> 
> Any idea why git is not smarter when pulling down the objects?

I think it's to minimize the traffic in the git protocol. If you just compare 
git commits, you can calculate the delta relatively quickly with fewer 
roundtrips. If server and client start to negotiate on the git object level 
itself it's going to take months to figure out which objects the client has and 
which ones are missing :)

Simon
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Tor Arne Vestbø]

On 24.04.12 16:04, ext Shezan Baig wrote:

On Tue, Apr 24, 2012 at 9:55 AM, Adam Roben  wrote:

In what situation does this cause issues?


Probably the biggest issue is for people who've been using
git.webkit.org and now want to try out GitHub. Since the commits are
distinct between the two repositories, they have to do a full clone to
make the switch.



In theory though, these users should be able to just add a remote to
their existing clone.  Then it will just sync the commit objects, and
not the trees and blobs.  Not ideal, they would have two different
'masters', but still doable, and not *that* much of an overhead.
Switching between the different masters should also be fast since the
trees will be the same.


Right, a fetch should ideally just pull down the commit objects, but it 
appears git does not have this optimization. If it did, I don't think 
the issue of two remote masters would be that big, since you would at 
some point likely transition to use one of the mirrors anyways. And if 
not, having multiple mirrors/remotes should be fine -- I'm using both 
the github and gitorious mirror without any issues.



But I agree these two repos should probably merge sooner rather than
later, just to avoid confusion for new users etc :)


I would support that if it means cleaning up the author-script (which 
I'm happy to do), and using that on webkit.org.


tor arne

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Shezan Baig]

On Tue, Apr 24, 2012 at 9:55 AM, Adam Roben  wrote:
>> In what situation does this cause issues?
>
> Probably the biggest issue is for people who've been using
> git.webkit.org and now want to try out GitHub. Since the commits are
> distinct between the two repositories, they have to do a full clone to
> make the switch.


In theory though, these users should be able to just add a remote to
their existing clone.  Then it will just sync the commit objects, and
not the trees and blobs.  Not ideal, they would have two different
'masters', but still doable, and not *that* much of an overhead.
Switching between the different masters should also be fast since the
trees will be the same.

But I agree these two repos should probably merge sooner rather than
later, just to avoid confusion for new users etc :)
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Tor Arne Vestbø]

On 24.04.12 15:55, ext Adam Roben wrote:

Probably the biggest issue is for people who've been using
git.webkit.org and now want to try out GitHub. Since the commits are
distinct between the two repositories, they have to do a full clone to
make the switch.


Any idea why git is not smarter when pulling down the objects?

tor arne
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Adam Roben]

On Tue, Apr 24, 2012 at 9:49 AM, Tor Arne Vestbø
 wrote:
> On 18.04.12 17:02, Simon Hausmann wrote:
>>
>> On Wednesday, April 18, 2012 06:53:46 AM ext Shezan Baig wrote:
>>>
>>> Hi WebKit,
>>>
>>> I've been using a fork of the following repo:
>>> https://github.com/WebKit/webkit
>>>
>>> However, yesterday there was discussion on #webkit that the SHA-1
>>> checksums
>>> on this repo are different from repo at git.webkit.org, which means folks
>>> working on both need to have both versions checked out.
>>
>>
>> I believe the reason for them being different is because in the github
>> repo the
>> commit author fields are resolved.
>
>
> That's correct. I'm the one running that mirror (along with the one at
> gitorious.org/webkit), and the import is done using an author-script that
> resolves author names and emails for a nicer history. The commit objects
> will be different, hence the different sha1s, but the tree and blob objects
> are the same.
>
> In what situation does this cause issues?

Probably the biggest issue is for people who've been using
git.webkit.org and now want to try out GitHub. Since the commits are
distinct between the two repositories, they have to do a full clone to
make the switch.

-Adam
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Tor Arne Vestbø]

On 18.04.12 17:02, Simon Hausmann wrote:

On Wednesday, April 18, 2012 06:53:46 AM ext Shezan Baig wrote:

Hi WebKit,

I've been using a fork of the following repo:
https://github.com/WebKit/webkit

However, yesterday there was discussion on #webkit that the SHA-1 checksums
on this repo are different from repo at git.webkit.org, which means folks
working on both need to have both versions checked out.


I believe the reason for them being different is because in the github repo the
commit author fields are resolved.


That's correct. I'm the one running that mirror (along with the one at 
gitorious.org/webkit), and the import is done using an author-script 
that resolves author names and emails for a nicer history. The commit 
objects will be different, hence the different sha1s, but the tree and 
blob objects are the same.


In what situation does this cause issues?

I'd like to keep the github/gitorious mirror with proper author names, 
so is it perhaps an alternative to move the webkit.org mirror to use the 
same author script? (which can also be cleaned up an improved to take 
into account names from changlogs vs commit-queue, etc).


tor arne
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Jarred Nicholls]

On Apr 24, 2012, at 9:07 AM, Adam Roben  wrote:

> On Wed, Apr 18, 2012 at 11:06 AM, Jarred Nicholls  wrote:
> (from correct address)
> 
> On Wed, Apr 18, 2012 at 11:06 AM, Jarred Nicholls  wrote:
> On Wed, Apr 18, 2012 at 11:02 AM, Simon Hausmann  
> wrote:
> On Wednesday, April 18, 2012 06:53:46 AM ext Shezan Baig wrote:
> > Hi WebKit,
> >
> > I've been using a fork of the following repo:
> > https://github.com/WebKit/webkit
> >
> > However, yesterday there was discussion on #webkit that the SHA-1 checksums
> > on this repo are different from repo at git.webkit.org, which means folks
> > working on both need to have both versions checked out.
> 
> I believe the reason for them being different is because in the github repo 
> the
> commit author fields are resolved.
> 
> Yeah that's totally it.  So svn.webkit.org => git.webkit.org => github would 
> need to be the mirroring strategy.  Sounds dicey :)
> 
>  
> I don't see what would be "dicey" about it. The svn.webkit.org -> 
> git.webkit.org step is the fragile one; after that it's just a simple "git 
> push" to get things over to GitHub. This sounds like a pretty good approach 
> to me, though of course it will cause some havoc for people who have already 
> been doing work using the current GitHub repository.

I was being facetious.  The notion of chaining repos is always "fun" but 
technically you're right; it's as easy as a push, and that is more or less 
immune to errors i.e. if a push failed due to some network or server issue it 
would just push again the next commit and be back on track.

> 
> -Adam
> 
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Adam Roben]

On Wed, Apr 18, 2012 at 11:06 AM, Jarred Nicholls  wrote:

> (from correct address)
>
> On Wed, Apr 18, 2012 at 11:06 AM, Jarred Nicholls wrote:
>
>> On Wed, Apr 18, 2012 at 11:02 AM, Simon Hausmann <
>> simon.hausm...@nokia.com> wrote:
>>
>>> On Wednesday, April 18, 2012 06:53:46 AM ext Shezan Baig wrote:
>>> > Hi WebKit,
>>> >
>>> > I've been using a fork of the following repo:
>>> > https://github.com/WebKit/webkit
>>> >
>>> > However, yesterday there was discussion on #webkit that the SHA-1
>>> checksums
>>> > on this repo are different from repo at git.webkit.org, which means
>>> folks
>>> > working on both need to have both versions checked out.
>>>
>>> I believe the reason for them being different is because in the github
>>> repo the
>>> commit author fields are resolved.
>>>
>>
>> Yeah that's totally it.  So svn.webkit.org => git.webkit.org => github
>> would need to be the mirroring strategy.  Sounds dicey :)
>>
>>
I don't see what would be "dicey" about it. The svn.webkit.org ->
git.webkit.org step is the fragile one; after that it's just a simple "git
push" to get things over to GitHub. This sounds like a pretty good approach
to me, though of course it will cause some havoc for people who have
already been doing work using the current GitHub repository.

-Adam
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Adam Roben]

Well that turned out ugly. Let's try again:

$ diff -u <(GIT_DIR=WebKit/.git git cat-file -p
df242ce698c19b591e975d88c29f7411b2f2963d) <(GIT_DIR=GitHubWebKit/.git git
cat-file -p 93f4255f7cb09996f0a9a354754c7902da87d1a3)
--- /dev/fd/63 2012-04-24 09:01:56.0 -0400
+++ /dev/fd/62 2012-04-24 09:01:56.0 -0400
@@ -1,7 +1,7 @@
 tree 492d5271473c516151a406aa02ebdbf1b494e758
-parent 1973d7515628dd8a4b3dd7559f0b0e2073096590
-author kl...@webkit.org

1335221533 +
-committer kl...@webkit.org

1335221533 +
+parent 9e00d90f6474a88108fe9d875d80ba2c04302733
+author Andreas Kling  1335221533 +
+committer Andreas Kling  1335221533 +

 [Mac] WebProcess should empty cache on a background thread/block.
 

-Adam

On Tue, Apr 24, 2012 at 9:03 AM, Adam Roben  wrote:
> On Wed, Apr 18, 2012 at 11:02 AM, Simon Hausmann
>  wrote:
>> On Wednesday, April 18, 2012 06:53:46 AM ext Shezan Baig wrote:
>>> Hi WebKit,
>>>
>>> I've been using a fork of the following repo:
>>> https://github.com/WebKit/webkit
>>>
>>> However, yesterday there was discussion on #webkit that the SHA-1
checksums
>>> on this repo are different from repo at git.webkit.org, which means
folks
>>> working on both need to have both versions checked out.
>>
>> I believe the reason for them being different is because in the github
repo the
>> commit author fields are resolved.
>
> That looks correct to me:
>
>
> $ diff -u <(GIT_DIR=WebKit/.git git cat-file -p
> df242ce698c19b591e975d88c29f7411b2f2963d) <(GIT_DIR=GitHubWebKit/.git
> git cat-file -p 93f4255f7cb09996f0a9a354754c7902da87d1a3)
> --- /dev/fd/63  2012-04-24 09:01:56.0 -0400
> +++ /dev/fd/62  2012-04-24 09:01:56.0 -0400
> @@ -1,7 +1,7 @@
>  tree 492d5271473c516151a406aa02ebdbf1b494e758
> -parent 1973d7515628dd8a4b3dd7559f0b0e2073096590
> -author kl...@webkit.org
>  1335221533
> +
> -committer kl...@webkit.org
>  1335221533
> +
> +parent 9e00d90f6474a88108fe9d875d80ba2c04302733
> +author Andreas Kling  1335221533 +
> +committer Andreas Kling  1335221533 +
>
>  [Mac] WebProcess should empty cache on a background thread/block.
>  
>
> You can see above that the tree and commit message are identical
> between the two repositories. But the author and committer are
> different, which causes the commit hash to be different (and since
> this is true for older commits as well, the parent hash is different
> too).
>
> -Adam
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Adam Roben]

On Wed, Apr 18, 2012 at 11:02 AM, Simon Hausmann
 wrote:
> On Wednesday, April 18, 2012 06:53:46 AM ext Shezan Baig wrote:
>> Hi WebKit,
>>
>> I've been using a fork of the following repo:
>> https://github.com/WebKit/webkit
>>
>> However, yesterday there was discussion on #webkit that the SHA-1 checksums
>> on this repo are different from repo at git.webkit.org, which means folks
>> working on both need to have both versions checked out.
>
> I believe the reason for them being different is because in the github repo 
> the
> commit author fields are resolved.

That looks correct to me:


$ diff -u <(GIT_DIR=WebKit/.git git cat-file -p
df242ce698c19b591e975d88c29f7411b2f2963d) <(GIT_DIR=GitHubWebKit/.git
git cat-file -p 93f4255f7cb09996f0a9a354754c7902da87d1a3)
--- /dev/fd/63  2012-04-24 09:01:56.0 -0400
+++ /dev/fd/62  2012-04-24 09:01:56.0 -0400
@@ -1,7 +1,7 @@
 tree 492d5271473c516151a406aa02ebdbf1b494e758
-parent 1973d7515628dd8a4b3dd7559f0b0e2073096590
-author kl...@webkit.org
 1335221533
+
-committer kl...@webkit.org
 1335221533
+
+parent 9e00d90f6474a88108fe9d875d80ba2c04302733
+author Andreas Kling  1335221533 +
+committer Andreas Kling  1335221533 +

 [Mac] WebProcess should empty cache on a background thread/block.
 

You can see above that the tree and commit message are identical
between the two repositories. But the author and committer are
different, which causes the commit hash to be different (and since
this is true for older commits as well, the parent hash is different
too).

-Adam
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Jarred Nicholls]

(from correct address)

On Wed, Apr 18, 2012 at 11:06 AM, Jarred Nicholls  wrote:

> On Wed, Apr 18, 2012 at 11:02 AM, Simon Hausmann  > wrote:
>
>> On Wednesday, April 18, 2012 06:53:46 AM ext Shezan Baig wrote:
>> > Hi WebKit,
>> >
>> > I've been using a fork of the following repo:
>> > https://github.com/WebKit/webkit
>> >
>> > However, yesterday there was discussion on #webkit that the SHA-1
>> checksums
>> > on this repo are different from repo at git.webkit.org, which means
>> folks
>> > working on both need to have both versions checked out.
>>
>> I believe the reason for them being different is because in the github
>> repo the
>> commit author fields are resolved.
>>
>
> Yeah that's totally it.  So svn.webkit.org => git.webkit.org => github
> would need to be the mirroring strategy.  Sounds dicey :)
>
>
>>
>>
>> Simon
>> ___
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>
>
>
>
> --
> 
>
> *Sencha*
> Jarred Nicholls, Senior Software Architect
> @jarrednicholls
> 
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Shezan Baig]

On Wed, Apr 18, 2012 at 11:02 AM, Simon Hausmann
wrote:
>
> I believe the reason for them being different is because in the github
> repo the
> commit author fields are resolved.
>
>


That would certainly explain it :)  I don't have a git.webkit.org checkout,
so I couldn't tell
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Simon Hausmann]

On Wednesday, April 18, 2012 06:53:46 AM ext Shezan Baig wrote:
> Hi WebKit,
> 
> I've been using a fork of the following repo:
> https://github.com/WebKit/webkit
> 
> However, yesterday there was discussion on #webkit that the SHA-1 checksums
> on this repo are different from repo at git.webkit.org, which means folks
> working on both need to have both versions checked out.

I believe the reason for them being different is because in the github repo the 
commit author fields are resolved.


Simon
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Shezan Baig]

(resending to all)

Yes, I think it would be better to mirror git.webkit.org to github instead
of mirroring from svn to github.
In theory, it really shouldn't make a difference though, so i'm actually
surprised that the sha1 are out of sync.
But mirroring from git.webkit.org will guarantee they are the same,
regardless of any wierdness that git-svn might do.


On Wed, Apr 18, 2012 at 10:00 AM, Jarred Nicholls  wrote:

> Wouldn't we need to continually mirror git.webkit.org to github as well?
>  I presume github is mirroring directly from svn right now.  I'd think the
> out-of-sync issue would simply occur again unless we started to mirror
> git.webkit.org to github instead of svn to github.
>
> I don't know what all Git takes into account when creating the sha1
> outside of content, tree and commit meta data, so I'm unsure if doing this
> git.webkit.org => github forced push would mean that future svn commits -
> being mirrored to both repos in parallel - would result in identical sha1
> hashes going forward...?
>
> Jarred
>
> On Wed, Apr 18, 2012 at 6:53 AM, Shezan Baig wrote:
>
>> Hi WebKit,
>>
>> I've been using a fork of the following repo:
>> https://github.com/WebKit/webkit
>>
>> However, yesterday there was discussion on #webkit that the SHA-1
>> checksums on this repo are different from repo at git.webkit.org, which
>> means folks working on both need to have both versions checked out.
>>
>> I believe the answer to this problem is in:
>> http://help.github.com/move-a-repo/
>>
>> (look at the last section titled "Manual clone and push")
>>
>> Anyone in the "WebKit" organization on https://github.com/WebKit should
>> be able to push this.  Once this is pushed, we can retire the existing repo
>> on github.  This means the existing forks will be unusable, but I think it
>> will be good to do this earlier rather than later, so we just have "one"
>> repo, and this will make it easier for existing git.webkit.org users to
>> switch to github.
>>
>> Thanks,
>> -shez-
>>
>>
>> ___
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>
>>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] github mirror

[Jarred Nicholls]

Wouldn't we need to continually mirror git.webkit.org to github as well?  I
presume github is mirroring directly from svn right now.  I'd think the
out-of-sync issue would simply occur again unless we started to mirror git.
webkit.org to github instead of svn to github.

I don't know what all Git takes into account when creating the sha1 outside
of content, tree and commit meta data, so I'm unsure if doing this git.
webkit.org => github forced push would mean that future svn commits - being
mirrored to both repos in parallel - would result in identical sha1 hashes
going forward...?

Jarred

On Wed, Apr 18, 2012 at 6:53 AM, Shezan Baig  wrote:

> Hi WebKit,
>
> I've been using a fork of the following repo:
> https://github.com/WebKit/webkit
>
> However, yesterday there was discussion on #webkit that the SHA-1
> checksums on this repo are different from repo at git.webkit.org, which
> means folks working on both need to have both versions checked out.
>
> I believe the answer to this problem is in:
> http://help.github.com/move-a-repo/
>
> (look at the last section titled "Manual clone and push")
>
> Anyone in the "WebKit" organization on https://github.com/WebKit should
> be able to push this.  Once this is pushed, we can retire the existing repo
> on github.  This means the existing forks will be unusable, but I think it
> will be good to do this earlier rather than later, so we just have "one"
> repo, and this will make it easier for existing git.webkit.org users to
> switch to github.
>
> Thanks,
> -shez-
>
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] github mirror

[Shezan Baig]

Hi WebKit,

I've been using a fork of the following repo:
https://github.com/WebKit/webkit

However, yesterday there was discussion on #webkit that the SHA-1 checksums
on this repo are different from repo at git.webkit.org, which means folks
working on both need to have both versions checked out.

I believe the answer to this problem is in:
http://help.github.com/move-a-repo/

(look at the last section titled "Manual clone and push")

Anyone in the "WebKit" organization on https://github.com/WebKit should be
able to push this.  Once this is pushed, we can retire the existing repo on
github.  This means the existing forks will be unusable, but I think it
will be good to do this earlier rather than later, so we just have "one"
repo, and this will make it easier for existing git.webkit.org users to
switch to github.

Thanks,
-shez-
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev