Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

git-new-workdir usage (was: [SCM] Web pages branch, master, updated. 7674ea1101a508e65b59b717d549c30b81c8a18e)

1 view
Skip to first unread message

Thomas Schwinge

unread,
Mar 19, 2013, 2:07:20 PM3/19/13
to toscan...@tiscali.it, bug-...@gnu.org
Hi Pino!

On Fri, 15 Mar 2013 22:39:07 +0000, Pino Toscano <toscan...@tiscali.it> wrote:
> commit 7674ea1101a508e65b59b717d549c30b81c8a18e
> Author: Pino Toscano <toscan...@tiscali.it>
> Date: Fri Mar 15 23:38:52 2013 +0100
>
> more changes

I don't understand your reasoning in source_repositories/incubator that a
»drawback is that updating a subrepository requires updating its branch
on the main clone first« -- I'm reasonably sure that I have more than
once been pushing back to different remote hosts directly from workdirs
created by git-new-workdir. Or haven't I understood what you're saying?
(And of course I do endorse git-new-workdir usage and daily use it
myself.)


Grüße,
Thomas

Pino Toscano

unread,
Mar 19, 2013, 2:18:38 PM3/19/13
to bug-...@gnu.org
Alle martedì 19 marzo 2013, Thomas Schwinge ha scritto:
> On Fri, 15 Mar 2013 22:39:07 +0000, Pino Toscano
<toscan...@tiscali.it> wrote:
> > commit 7674ea1101a508e65b59b717d549c30b81c8a18e
> > Author: Pino Toscano <toscan...@tiscali.it>
> > Date: Fri Mar 15 23:38:52 2013 +0100
> >
> > more changes
>
> I don't understand your reasoning in source_repositories/incubator
> that a »drawback is that updating a subrepository requires updating
> its branch on the main clone first« -- I'm reasonably sure that I
> have more than once been pushing back to different remote hosts
> directly from workdirs created by git-new-workdir.

To be honest, I've never tried to pull from subrepos without having
updated the main repository first; I guess it would just update in the
main repository only the branch followed by that subrepo.

That part could be removed then, no big deal.

--
Pino Toscano
signature.asc
0 new messages