40 minutes ago, Sam Tobin-Hochstadt wrote:
> On Tue, Aug 13, 2013 at 5:10 PM, Tony Garnock-Jones wrote:
> > On 08/13/2013 05:05 PM, Nick Shelley wrote:
> >>
> >> I was mainly asking about the intermediate form because it seems
> >> like it could be useful, but I didn't understand how it would
> >>
On Tue, Aug 13, 2013 at 5:10 PM, Tony Garnock-Jones wrote:
> On 08/13/2013 05:05 PM, Nick Shelley wrote:
>>
>> I was mainly asking about the intermediate form because it seems like it
>> could be useful, but I didn't understand how it would work.
>
>
> One major difference I've just spotted is tha
On 08/13/2013 05:05 PM, Nick Shelley wrote:
I was mainly asking about the intermediate form because it seems like it
could be useful, but I didn't understand how it would work.
One major difference I've just spotted is that git submodules are tied
to particular commit IDs, leading to detached-
On 08/13/2013 04:49 PM, Tony Garnock-Jones wrote:
Perhaps you're right. Maybe my impression that git submodules are frozen
is out-of-date. It has been a while since I used them. Perhaps they're
first-class checkouts that can be manipulated independently of their...
supermodule. If that's true, pe
Although I like being right, I'm not sure what I'm right about. We use
submodules at work both to include third-party tools and to share code
among related internal projects. Submodules have worked fine for us so far,
but they also have their downsides. For instance, we've made changes to
shared su
On 08/13/2013 04:42 PM, Nick Shelley wrote:
Can you elaborate on your intermediate form? I don't understand how git
submodules prohibit or restrict submodule evolution. The only difference
I see with the submodule approach is that it requires an extra commit to
update the submodule versions (and
Can you elaborate on your intermediate form? I don't understand how git
submodules prohibit or restrict submodule evolution. The only difference I
see with the submodule approach is that it requires an extra commit to
update the submodule versions (and subsequently a pull followed by a
submodule up
Hi all,
Matthias asked me to write a few words about an experience I had
splitting a large repository of code up into smaller repositories and
then building a mechanism to tie them together again.
== A short story ==
Once upon a time, RabbitMQ (www.rabbitmq.com) was held in a single,
monoli
8 matches
Mail list logo
