Finished going through and nailed the rest of the open issues!
# Irrelevant but it seems like someone should take a look
511 466
# Irrelevant to git-scm.com and should be closed
599 596 570 565 563 558 538 537 520 511 509 507 501 494 465
# Resolved, duplicate, or non-issue
596 593 592 588
On Mon, Feb 06, 2017 at 12:49:34PM -0800, Junio C Hamano wrote:
> Of course, that will make it easier to let broken objects created by
> newer reimplementations of Git (and bugs in our code that cause us
> to create such broken objects) go unnoticed, so we would want to
> keep them at warn (not ig
Jeff King writes:
> [1] If we had a more permissive set of defaults, it would probably make
> sense to turn on fsckObjects by default. Some of the checks are
> security-relevant, like disallowing trees with ".GIT",
> "../../etc/passwd", etc. Those _should_ be handled sanely by the
>
On Mon, Feb 06, 2017 at 05:18:03PM +0700, Duy Nguyen wrote:
> On Mon, Feb 6, 2017 at 1:15 PM, Samuel Lijin wrote:
> > # Irrelevant but someone should take a look
> >
> > 693
>
> To save people some time (and since i looked at it anyway), this is
> about whether "warning in tree xxx: contains zer
On Mon, Feb 06, 2017 at 12:15:08AM -0600, Samuel Lijin wrote:
> I've went through a bunch of open issues on the git/git-scm.com repo
> (specifically, everything after #600) and I think the bulk of them can
> be closed.
>
> I've taken the liberty of classifying them as shown below.
Thanks, this i
On Mon, Feb 6, 2017 at 1:15 PM, Samuel Lijin wrote:
> # Irrelevant but someone should take a look
>
> 693
To save people some time (and since i looked at it anyway), this is
about whether "warning in tree xxx: contains zero-padded file modes:
from fsck should be a warning or error. It is a warnin
Adding Peff to cc as he is the current maintainer of the git-scm.com site/repo.
On Mon, Feb 6, 2017 at 7:15 AM, Samuel Lijin wrote:
>
> I've taken the liberty of classifying them as shown below.
>
As a community member who cares a lot about that site, thank you! I
would love to contribute by rev
I've went through a bunch of open issues on the git/git-scm.com repo
(specifically, everything after #600) and I think the bulk of them can
be closed.
I've taken the liberty of classifying them as shown below.
- Sam
# Irrelevant but someone should take a look
693
# Irrelevant to git-scm.com
8 matches
Mail list logo