From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: [GSoC] Some #leftoverbits for anyone looking for little projects
Date: Sat, 17 Mar 2018 22:20:40 +0100 [thread overview]
Message-ID: <87in9ucsbb.fsf@evledraar.gmail.com> (raw)
In lieu of sending a PR to https://git.github.io/SoC-2018-Microprojects/
I thought I'd list a few more suggestions, and hopefully others will
chime in.
This is all TODO stuff I've been meaning to do myself, but wouldn't mind
at all if someone else tackled.
I'm not interested in mentoring GSoC, but these are all small enough to
need to special help from me (or anyone in particular), and if nobody
picks them up I can refer back to this mail for my own use.
* Having grep support the -o option like GNU grep et al.
We have most of the code for this already in the form of our color
hi-lighting, it would mostly just be a matter of "just print out the
stuff you'd have colored", with the small exception that if you have
more than one match on a line they should be printed out on their own
lines.
* Give "rebase -i" some option so when you "reword" the patch is
included in the message.
I keep going to the shell because I have no idea what change I'm
describing.
* Add more config IncludeIf conditions.
Recently there was a mention on git-users to excend the includeIf
statement to read config:
https://groups.google.com/forum/?fromgroups#!searchin/git-users/includeif%7Csort:date/git-users/SHd506snwSk/UdVCsCILBwAJ
Now that seems like a nasty circular dependency but there's other
low-hanging fruit there, like make it match a given env name to a
value (or glob?).
* Add another set of GIT_{AUTHOR,COMMITTER}_{NAME,EMAIL} with lower
priorities.
There is a script at work which I have to manually blacklist which
sets git author names & e-mails via LDAP for all logged in users via
/etc/profile (and gets my name wrong)[1].
It would be nice if git supported a way to do this that didn't either
involve overriding everything (as the current env vars do) or munging
the user's ~ config (ew!). I.e. the priority of these new env vars
would come after reading from the config, not overriding the config
as the current ones do. So it could be used to make a suggestion if
no other value was found.
* Write git-unpack-{refs,objects}
I don't know if this is small enough (maybe the refs part?). This
would give you purely loose objects & refs. This is a terrible idea
for any "real" use, but very useful for testing.
Now when I'm testing repack I need to keep an old copy of the repo
around, because there's no easy way (that I know of) to pack things
and then get back to loose object state. Ditto for packing refs.
* I had a previous TODO list of "small" things at
https://public-inbox.org/git/CACBZZX5wdnA-96e11edE7xRnAHo19RFTrZmqFQj-0ogLOJTncQ@mail.gmail.com/
1. At work like in so many companies LDAP is synced everywhere, but of
course that means catering to the lowest common denominator. Last I
heard attempts to give me a non-ASCII name (in the GEOS field) had
failed because some phone or printer somewhere refused to accept it.
next reply other threads:[~2018-03-17 21:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 21:20 Ævar Arnfjörð Bjarmason [this message]
2019-05-20 18:23 ` [GSoC] Some #leftoverbits for anyone looking for little projects Matheus Tavares
2019-05-20 23:49 ` Ævar Arnfjörð Bjarmason
2019-05-21 4:38 ` Matheus Tavares Bernardino
2019-05-28 10:37 ` Johannes Schindelin
2019-05-28 17:37 ` Matheus Tavares Bernardino
2019-05-28 18:16 ` Johannes Schindelin
2019-05-29 9:38 ` Johannes Schindelin
2019-05-29 9:40 ` Johannes Schindelin
[not found] ` <20220318220623.50528-1-gaurijove@gmail.com>
[not found] ` <CANsrJQdNKiX93GnVXztmvYQQBxr6-HsYNx5UvYXSFg32Op3ZPQ@mail.gmail.com>
[not found] ` <CANsrJQe1YuggxdBHdSdukXRj3myVCTNwLiiWNLrAzPpzA4FOOA@mail.gmail.com>
[not found] ` <220319.86ee2yds2f.gmgdl@evledraar.gmail.com>
[not found] ` <CANsrJQdJ1wBThUyJ=QSt6NwU8HzQY2VaWc11UfZQ+ktRQs_YTQ@mail.gmail.com>
[not found] ` <220319.86a6dlewyj.gmgdl@evledraar.gmail.com>
2022-03-20 19:14 ` Having grep support the -o option Jayati Shrivastava
2022-03-22 6:08 ` Christian Couder
2022-03-22 10:50 ` Ævar Arnfjörð Bjarmason
2022-03-23 17:45 ` Jayati Shrivastava
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87in9ucsbb.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).