[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#979188: marked as done (RFS: git-subrepo/0.4.9-3 [ITP] -- Alternative to git-submodule(1) and git-subtree(1))

Your message dated Mon, 17 Feb 2025 10:25:37 +0800
with message-id <CAKq8=3LAiv6c5GxqLEqUrw+5Mc_eLTA_8dRcAhHYmCed4QPYpw@mail.gmail.com>
and subject line Close #979188
has caused the Debian Bug report #979188,
regarding RFS: git-subrepo/0.4.9-3 [ITP] -- Alternative to git-submodule(1) and git-subtree(1)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
979188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979188
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "git-subrepo":

 * Package name    : git-subrepo
   Version         : 0.4.3-1
   Upstream Author : Ingy döt Net <ingy@ingy.net>
 * URL             : https://github.com/ingydotnet/git-subrepo
 * License         : GPL-2+ and GPL-2, MIT
 * Vcs             : https://salsa.debian.org/guest-dxld/git-subrepo
   Section         : vcs

git-subrepo allows embedding and managing copies of other git repositories
in your repo for purposes such as vendoring.

Commits in the parent repo involving the subrepo can easily be pushed back
upstream even when they touch files outside the subrepo -- these will simply
be omitted.

Pulling new upstream commits back into your repo is naturally also possible.

git-subrepo is designed such that only the maintainer of a repo will
actually need to have it installed, contributors only need to do so if
they wish to push/pull from the subrepo's upstream and user should never
have to interact with git-subrepo at all since all of a subrepos file are
available right after a plain git-clone.

This is unlike git-submodule(1)s where all users and contributors must be
aware of their presence and deal with them.

git-subrepo is in principle somewhat similar to git-subtree(1) as it also
embedds snapshot copies of other repos, however it is much easier to use
and the way the history is kept is less convoluted. Pulling any number of
new commits from a subrepo's upstream will result in only a single commit
in the parent repo for example.

It builds this binary package:

  git-subrepo - Alternative to git-submodule(1) and git-subtree(1)

To access further information about this package, please visit the following URL:

  https://mentors.debian.net/package/git-subrepo/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/g/git-subrepo/git-subrepo_0.4.3-1.dsc

Changes for the initial release:

 git-subrepo (0.4.3-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #911397)

Regards,
Daniel

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Uploaded.

--- End Message ---
Reply to: