On 15.06.2016 [08:40:20 -0700], Nish Aravamudan wrote: > On 15.06.2016 [08:39:01 -0700], Nish Aravamudan wrote: > > On 15.06.2016 [15:13:48 +0300], Louis Bouchard wrote: > > > Hi, > > > > > > Le 15/06/2016 14:15, Robie Basak a écrit : > > > > On Wed, Jun 15, 2016 at 09:17:46AM +0300, Louis Bouchard wrote: > > > >> Is there a specific procedure to include the new releases from debian > > > >> in the > > > >> existing repo ? Should I just use git-dsc-import of the new source > > > >> packages over > > > >> the existing debian/sid tag ? > > > > > > > > I think we just reimport. > > > > > > > > > > Imagine having to reimport when most of the merge work has been done. > > > We can still use the old repo as remote & cherry-pick but wouldn't it > > > be possible to only import the new delta ? > > > > > > I'm not familiar enough with usd-import to know if only bringing in > > > the delta is possible. > > > > Yes, it will just update the (remote) tree with versions it hasn't seen. > > Does that mean you want me to update the corosync repository?
Done: ./usd-import -o usd-import-team corosync Importing 2.3.5-8 to debian/sid Importing 2.3.5-9 to debian/sid Importing 2.3.5-9 to debian/stretch As far as your merge goes, you should be able to rebase your existing merge on to the new remote/debian/sid (after running `git fetch remote`) and then propose an updated MR. -Nish -Nish -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam