public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Git without SSH Server and cygrunsrv
Date: Mon, 03 Jul 2017 12:25:00 -0000	[thread overview]
Message-ID: <20170703122510.GC26574@dinwoodie.org> (raw)
In-Reply-To: <312b3b9b-a2f5-424f-53af-4ff347158560@x76.eu>

On Wed, Jun 14, 2017 at 12:35:13PM +0700, mlists wrote:
> Thank you for the explanation Adam.
> 
> Last question: How much more is the workload for maintaining a "splitted
> package"?
> 
> I understand I can contribute with patches but if it would increase the
> workload for the maintainers, then I think there's no point in doing it.

Once the patch is submitted and tested, it's effectively zero extra
work.  Yaakov has now submitted a patch for this, so I just need to
test that works as expected (and in particular nothing non-p4 related is
obviously broken if the new git-p4 package isn't installed), then I'll
be able to publish it.

As I've said elsewhere, my time as Git maintainer is currently focused
on getting the latest upstream release working on Cygwin at all, so it
may be a short while before I can do the testing, but it will hopefully
happen soon...

Adam

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-07-03 12:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13  0:13 mlists
2017-06-13  4:00 ` Marco Atzeri
2017-06-13 10:22   ` Adam Dinwoodie
2017-06-14  5:39     ` mlists
2017-07-03 12:25       ` Adam Dinwoodie [this message]
2017-06-15 16:41     ` [PATCH git] Separate git-p4 subpackage Yaakov Selkowitz
2017-07-03 12:21       ` Adam Dinwoodie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170703122510.GC26574@dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).