Skip to content

Commit 6bb57ec

Browse files
committed
rn-13: fixes from Junio
1 parent afab0f4 commit 6bb57ec

File tree

1 file changed

+29
-18
lines changed

1 file changed

+29
-18
lines changed

rev_news/drafts/edition-13.md

Lines changed: 29 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -21,23 +21,30 @@ This edition covers what happened during the month of February 2016.
2121

2222
* [RFC: Resumable clone based on hybrid "smart" and "dumb" HTTP](http://thread.gmane.org/gmane.comp.version-control.git/285921/)
2323

24-
It is a well known problem that `git clone` is not resumable. If the
24+
It is a widely known problem that `git clone` is not resumable. If the
2525
connection comes down during a clone, the clone has to be restarted
2626
from scratch.
2727

28-
A work around that is often suggested is to use `git bundle` first, then
29-
to rsync that bundle and eventually to clone using the rsync'ed bundle. Some
30-
tools [like gitolite](http://thread.gmane.org/gmane.comp.version-control.git/235040/) have even been making it easier to support that.
28+
A work around that is often suggested and used is to first create a
29+
bundle using `git bundle`, to rsync that bundle, then to clone from
30+
the rsync'ed bundle and eventually to fetch what is missing from the
31+
remote git repository. Some tools
32+
[like gitolite](http://thread.gmane.org/gmane.comp.version-control.git/235040/) or
33+
[the "repo" tool that is used by AOSP](https://source.android.com/source/using-repo.html)
34+
and some websites
35+
[like kernel.org](https://www.kernel.org/)
36+
have even been making it easier to support that.
3137

3238
There was also at one point in 2011
3339
[a patch series](http://thread.gmane.org/gmane.comp.version-control.git/185196/)
3440
to improve the support of this kind of clone workflow internally.
3541

36-
And for some time this was thought of as just a small manpower problem. A
37-
few month of dedicated work by anyone could probably fix that. It was
38-
even proposed as a Google Summer of Code (GSoC) project.
42+
And for some time this was thought of by some Git developers as just a
43+
small manpower problem. A few month of dedicated work by anyone could
44+
probably fix that. It was even proposed as a Google Summer of Code
45+
(GSoC) project.
3946

40-
Over time though Git developers realized that it was not so easy
47+
Over time though the community realized that it was not so easy
4148
because some very careful design was needed, and it was removed from
4249
the list of possible GSoC projects.
4350

@@ -80,18 +87,22 @@ developer, and it's interesting to see Linux Kernel developers
8087
interested again in taking part in Git development. It reminds some
8188
old timers about the "good old time".
8289

83-
All these proposals have been discussed by many important Git
84-
developers and reviewers like Stefan Beller, Junio Hamano, Johannes
85-
Schindelin, Jonathan Nieder, Eric Sunshine, Jeff King, Elia Pinto.
90+
All these proposals have been discussed by many regular Git developers
91+
and reviewers like Stefan Beller, Junio Hamano, Johannes Schindelin,
92+
Jonathan Nieder, Eric Sunshine, Jeff King, Elia Pinto.
8693

87-
About Shawn's proposal there was also an interesting potential
88-
security issue called out by Blake Burkhart. And other people like
89-
Bhavik Bavishi and Konstantin Ryabitsev also took part of the
90-
discussion following Josh's email.
94+
About Shawn's proposal Blake Burkhart reminded the community that the
95+
implementation has to keep in mind that it would introduce potential
96+
security issue if Shawn's proposal is done carelessly. And other
97+
people like Bhavik Bavishi and Konstantin Ryabitsev also took part in
98+
the discussion following Josh's email.
9199

92100
From the last discussions about Josh's email, it appeared that Git
93-
developers favored Shawn's proposal over others, and maybe that
94-
Shawn's proposal was going to be worked on soon.
101+
developers favored Shawn's proposal over others, though Shawn's
102+
proposal could benefit from implementing parts of Al's and Josh's
103+
proposal too. So the plan seemed to be that Shawn's proposal was going
104+
to be worked on soon, and then later some optimizations from Al and
105+
Josh could be implemented on top of it.
95106

96107
Then on March 5 Kevin Wern sent
97108
[an email called "Resumable clone"](http://thread.gmane.org/gmane.comp.version-control.git/288306/),
@@ -248,4 +259,4 @@ __Git tools and sites__
248259

249260
This edition of Git Rev News was curated by Christian Couder &lt;<[email protected]>&gt;,
250261
Thomas Ferris Nicolaisen &lt;<[email protected]>&gt; and Nicola Paolucci &lt;<[email protected]>&gt;,
251-
with help from Josh Triplett.
262+
with help from Junio Hamano and Josh Triplett.

0 commit comments

Comments
 (0)