| 1 |
On Sat, Jun 2, 2012 at 12:59 PM, Rich Freeman <rich0@g.o> wrote: |
| 2 |
> Looks useful. Wasn't aware that a bundle was something other than a tarball. |
| 3 |
> |
| 4 |
> We'll probably need to spell out the preferred process in the docs, |
| 5 |
> and reference it frequently in communications. Otherwise you'll get |
| 6 |
> quite a few clones instead. |
| 7 |
> |
| 8 |
> It appears that devs will have to add the remote for the live |
| 9 |
> repository after they've cloned the bundle - otherwise they'll just |
| 10 |
> keep pulling from the bundle which isn't all that convenient. |
| 11 |
|
| 12 |
I think you still misunderstand. As I understand Robin, we wouldn't |
| 13 |
even offer up a clone of the full-history bundle, it would only be |
| 14 |
offered as a normal download. The default workflow is cloning from the |
| 15 |
shallow version, which will obviously give you the desired remote. |
| 16 |
|
| 17 |
Cheers, |
| 18 |
|
| 19 |
Dirkjan |
Archives