Re: (topgit question) deleting a dependency

["Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>]

Hello,

> >> This is a little beyond my comprehension :(  However, this
> >> is also why I am limiting myself to
> >> 
> >>   - a single level of dependencies in tg, (master -->
> >>     multiple t/something --> t/all), and
> >> 
> >>   - no changes of its own in t/all
> >> 
> >> When any of the t/something graduates to master, t/all will
> >> be blown away (safe, since it has no changes of its own) and
> 
> > What makes you think it will "be blown away"?  Or alternatively, what do
> 
> My mistake.  I meant that I will blow it away myself, and
> create a new one with the same name except it's list of deps
> will exclude the one that graduated.
> 
> > you mean saying that?  I often use the same approach and I never had the
> > feeling anything is blown away.  If upstream uses your t/something patch
> > it just merges into t/something making it empty without changing the
> 
> How?  When I update master from upstream and then tg update
> on t/all?
yes.  I think it's even save to just remove empty dependencies (and add
the dependencies of the patch branch to be deleted) from .topdeps.

Best regards
Uwe

-- 
Pengutronix e.K.                              | Uwe Kleine-König            |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |