Hi Daniel,
i prepared another candidate for the 0.4.6-1 release (
https://salsa.debian.org/spog/git-subrepo/-/commit/f96eeedd0e96b6f2bbcc8c013909de5d5325cafe
), hoping it ticks all the boxes and more:)
I made the PR upstream (https://github.com/ingydotnet/git-subrepo/pull/623) and
added
patches if necessary.
>
> From a quick look it seems removing the `git config core.autocrlf input`
> call in test/setup already gets us quite far but the way git subrepo finds
> its libs needs adjustment too.
>
> Commit review below:
>
> > From: Samo Pogačnik
> &g
t's not working and fix it
> with more upstreamable patches if necessary.
>
> From a quick look it seems removing the `git config core.autocrlf input`
> call in test/setup already gets us quite far but the way git subrepo finds
> its libs needs adjustment too.
>
> Commi
Hi Daniel,
Dne 28.05.2024 (tor) ob 19:23 +0200 je Daniel Gröber napisal(a):
> I'm not super happy with the approach of putting git-subrepo.d inside
> /usr/share/git-subrepo tbh. I might be able to let it pass but it seems
> lintian found another issue that needs patching anyway so you may as well
Dne 06.05.2024 (pon) ob 15:02 +0200 je Daniel Gröber napisal(a):
>
> Hmm. I'm not sure I like the idea of abusing libexec in this
> way. Technically speaking it's for "internal binaries that are not intended
> to be executed directly by users or shell scripts" this is clearly not the
> case here.
Hi Daniel,
Dne 06.05.2024 (pon) ob 15:02 +0200 je Daniel Gröber napisal(a):
>
> To be clear force-push should never ever be done when collaborating on the
> branche(s) with multiple people, except in the most dire of circumstances
> and only if everyone involved is notified appropriately. I'll
Dne 01.05.2024 (sre) ob 23:09 +0200 je Samo Pogačnik napisal(a):
> Hi Daniel,
>
> After installing our current 'git-subrepo' deb i noticed, that bash-completion
> integration with git does not work. The git-subrepo's own bash completion
> works,
> after you've already typed t
Hi Daniel,
After installing our current 'git-subrepo' deb i noticed, that bash-completion
integration with git does not work. The git-subrepo's own bash completion works,
after you've already typed the first two words 'git subrepo TAB TAB', but the
initial recognition of the 'subrepo' sub-command
Dne 25.04.2024 (čet) ob 12:59 +0200 je Daniel Gröber napisal(a):
> On Wed, Apr 24, 2024 at 10:06:49PM +0200, Samo Pogačnik wrote:
> > Ok, so i'll prepare merge request in salsa gitlab, after pushing my
> > change in my working branch?
>
> So creating a MR is fine but it'
Hi Daniel,
Dne 24.04.2024 (sre) ob 17:33 +0200 je Daniel Gröber napisal(a):
> I'll push the repo there and give you access, you just have to adjust the
> Vcs-* fields and get those changes to me in a way that I actually want to
> accept them ;P
>
> FYI: I'm not being obtuse, I could ofc. just
;what changed since the last version" in the end, not a blow
> by blow of the git changes we used to get there. It's a judgement call tho.
>
> +
> + [ Samo Pogačnik ]
> + * Updated debian/control info
>
> Needs to be a lot more specifict than that. In d/changelog you're ta
Hi Daniel,
Dne 18.03.2024 (pon) ob 13:55 +0100 je Daniel Gröber napisal(a):
>
> A good place to start is https://wiki.debian.org/Packaging
>
> If you prefer a talk format there's Lucas' (excellent) tutorial
>
https://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.en.pdf
> I
Dne 11.03.2024 (pon) ob 20:18 +0100 je Daniel Gröber napisal(a):
> Hi Samo,
>
> wouldn't you know it I've become a DD before I got a response to the
> git-subrepo ITP/RFS ;) I also completely forgot about it until I needed it
> just now.
>
> Are you still interested in maintaining git-subrepo in
Hi Daniel,
I prepared a new git-subrepo in salsa as a fork of your project (
https://salsa.debian.org/spog/git-subrepo). Then i updated upstream and prepared
a new 'debian/sid' branch. Would you be so kind to take a look at it and comment
on what should be changed/fixed and how to proceed.
Hi Daniel,
Dne 24.03.2024 (ned) ob 17:46 +0100 je Daniel Gröber napisal(a):
> For building I use debuild or git-buildpackage+sbuild depending on context.
>
> I create chroots for sbuild with a wrapper script around
> sbuild-createchroot using btrfs-snapshots for efficiency.
>
> To keep working
Hi Daniel,
just a quick update.
Dne 01.04.2024 (pon) ob 23:07 +0200 je Daniel Gröber napisal(a):
>
> Anyway gbp has reasonably good documentation, maybe you haven't seen it yet:
> http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.intro.html
> (note the navigation buttons in the
Hi Daniel,
Dne 31.03.2024 (ned) ob 16:01 +0200 je Daniel Gröber napisal(a):
>
> You removed the (Closes Bug#) ITP reference from d/changelog. It's policy
> to close that but with the first upload, so you have to keep it.
>
Fixed (even salsa pipeline is happy:).
> Workflow wise I don't see why
brepo work when run in a worktree
* Simplify finding subrepos
* Ask git to find the .gitrepo files
* Doc: fix sentence repetition
* Fix typos
* Fixed typo
* Travis CI not checking out a branch.
Regards,
--
Samo Pogačnik
brepo work when run in a worktree
* Simplify finding subrepos
* Ask git to find the .gitrepo files
* Doc: fix sentence repetition
* Fix typos
* Fixed typo
* Travis CI not checking out a branch.
Regards,
--
Samo Pogačnik
t versions
* Make subrepo work when run in a worktree
* Simplify finding subrepos
* Ask git to find the .gitrepo files
* Doc: fix sentence repetition
* Fix typos
* Fixed typo
* Travis CI not checking out a branch.
Regards,
--
Samo Pogačnik
20 matches
Mail list logo
