Remove empty and redundant documentation files from the
Documentation/technical/ directory.
The empty doc files included only TODO messages with no documentation for
years. Instead an approach is being taken to keep all doc beside the code in
the relevant header files. Having empty doc files is co
Move the documentation from Documentation/technical/api-config.txt into
config.h as it's easier for the developers to find the usage information
beside the code instead of looking for it in another doc file, also
documentation/technical/api-config.txt is removed because the information it
has is no
[snip]
> >
> > > I'm happy to discuss possible projects if anybody has an idea but isn't
> > > sure how to develop it into a proposal.
> >
> > I'm new to Outreachy and programs like this, so does anyone have an
> > opinion on my draft proposal
Remove empty and redundant documentation files from the
Documentation/technical/ directory.
As part of moving the documentation from Documentation/technical/api-* to
header files, the following files are deleted because they include only TODO
messages with no documentation: Documentation/technical
El lun., 21 oct. 2019 a las 20:35, Emily Shaffer
() escribió:
>
> On Mon, Oct 21, 2019 at 12:39:16PM +0200, Miriam R. wrote:
> > Dear Git developers,
> > I’m an Outreachy applicant, I would like to make my contribution to
> > apply to this Outreachy internship period.
>
Hi Karina,
Please see my answer below.
On Mon, Oct 21, 2019 at 6:59 PM Karina Saucedo
wrote:
>
> Hello, my name is Karina and I'm and Outreachy applicant.
> I´m interested in applying to the project 'Add did you mean hints´ and
> I was wondering how can I start contributi
Move the documentation from Documentation/technical/api-config.txt into
config.h
Signed-off-by: Heba Waly heba.w...@gmail.com [heba.w...@gmail.com]
Thanks for taking the time to contribute to Git! Please be advised that the
Git community does not use github.com for their contributions. Instead, w
On Mon, Oct 21, 2019 at 11:54:01AM -0500, Karina Saucedo wrote:
> Hello, my name is Karina and I'm and Outreachy applicant. I´m interested in
> applying to the project 'Add did you mean hints´ and I was wondering how
> can I start contributing since there seem to be no issues o
On Mon, Oct 21, 2019 at 12:39:16PM +0200, Miriam R. wrote:
> Dear Git developers,
> I’m an Outreachy applicant, I would like to make my contribution to
> apply to this Outreachy internship period.
Welcome, Miriam! Good to hear from you.
>
> I have found this issue tag
Hello, my name is Karina and I'm and Outreachy applicant.
I´m interested in applying to the project 'Add did you mean hints´ and
I was wondering how can I start contributing since there seem to be no
issues on the github page. Thank you!
Dear Git developers,
I’m an Outreachy applicant, I would like to make my contribution to
apply to this Outreachy internship period.
I have found this issue tagged as open and goodfirstissue:
https://github.com/gitgitgadget/git/issues/230
But there is a PR from 4 months ago:
https://github.com
git format-patch
Hello everyone,
My name is Heba and I’m one of the Outreachy applicants. I’ve selected
the ‘moving the doc to comments’ microproject, and I’ll be submitting
several patches addressing this area during the next week or two. The
first one is already out there waiting for feedback (yey)
https
On Mon, Oct 14, 2019 at 02:46:29PM -0700, Jonathan Tan wrote:
> > > Well, I agree that it could be better, but with the C language as we
> > > have it now, I still slightly prefer an enum to a list of #define. Both
> > > ways, we still have to manually enter values for each flag, but with
> > > enu
On Mon, Oct 14, 2019 at 11:27:54AM -0700, Jonathan Tan wrote:
> > Jonathan Tan writes:
> >
> > >> > Also, I have a slight preference for putting "= 02" on the BLAME_COPY
> > >> > line but that is not necessary.
> > >>
> > >> That is absolutely necessary; it is not like "we do not care what
> > >
> > Well, I agree that it could be better, but with the C language as we
> > have it now, I still slightly prefer an enum to a list of #define. Both
> > ways, we still have to manually enter values for each flag, but with
> > enum, we get better debugger display (at least in gdb) and in the
> > fun
On Mon, Oct 14, 2019 at 11:27:54AM -0700, Jonathan Tan wrote:
> > Jonathan Tan writes:
> >
> > >> > Also, I have a slight preference for putting "= 02" on the BLAME_COPY
> > >> > line but that is not necessary.
> > >>
> > >> That is absolutely necessary; it is not like "we do not care what
> > >
> Jonathan Tan writes:
>
> >> > Also, I have a slight preference for putting "= 02" on the BLAME_COPY
> >> > line but that is not necessary.
> >>
> >> That is absolutely necessary; it is not like "we do not care what
> >> exact value _COPY gets; it can be any value as long as it is _MOVE
> >> pl
Jonathan Tan writes:
>> > Also, I have a slight preference for putting "= 02" on the BLAME_COPY
>> > line but that is not necessary.
>>
>> That is absolutely necessary; it is not like "we do not care what
>> exact value _COPY gets; it can be any value as long as it is _MOVE
>> plus 1", as these
On Fri, Oct 11, 2019 at 11:48:03AM -0700, Jonathan Tan wrote:
> > > Any reason why the names are renamed to omit "PICKAXE_"? In particular,
> > > these names are still global, so it is good to retain the extra context.
> > >
> > > (This doesn't mean that you are wrong to remove them - I just gave
> > Any reason why the names are renamed to omit "PICKAXE_"? In particular,
> > these names are still global, so it is good to retain the extra context.
> >
> > (This doesn't mean that you are wrong to remove them - I just gave my
> > opinion, and a reason for my opinion. If you had a reason to re
> Jonathan Tan writes:
>
> >> - if ((opt & PICKAXE_BLAME_COPY_HARDEST)
> >> - || ((opt & PICKAXE_BLAME_COPY_HARDER)
> >> + if ((opt & BLAME_COPY_HARDEST)
> >> + || ((opt & BLAME_COPY_HARDER)
> >
> > Any reason why the names are renamed to omit "PICKAXE_"? In particular,
> > these name
On Thu, Oct 10, 2019 at 11:44:39AM -0700, Jonathan Tan wrote:
> > Convert pickaxe_blame preprocessor constants in blame.h to an enum.
> > Also replace previous instances of the constants with the new enum values.
>
> First of all, thanks for your initiative in finding a microproject and
> making a
On Wed, Oct 09, 2019 at 07:25:51PM +0200, SZEDER Gábor wrote:
> > Probably they'd be easy enough to fix (and they're out of tree anyway),
> > so I'm not really arguing against the escape hatch exactly. Mostly I'm
> > just surprised that if I introduced 3 cases (out of probably a dozen
> > scripts)
Jonathan Tan writes:
>> -if ((opt & PICKAXE_BLAME_COPY_HARDEST)
>> -|| ((opt & PICKAXE_BLAME_COPY_HARDER)
>> +if ((opt & BLAME_COPY_HARDEST)
>> +|| ((opt & BLAME_COPY_HARDER)
>
> Any reason why the names are renamed to omit "PICKAXE_"? In particular,
> these names are stil
> Hello Jonathan!
> My name is Wambui and I'm one of the applicants in the current round of
> Outreachy applications. I wanted to write an initial email to introduce
> myself since I'm interested in working on your mentored projects!
>
> I have been going through th
> Convert pickaxe_blame preprocessor constants in blame.h to an enum.
> Also replace previous instances of the constants with the new enum values.
First of all, thanks for your initiative in finding a microproject and
making a patch for it!
About your commit message title, I know that 50 characte
Convert pickaxe_blame preprocessor constants in blame.h to an enum.
Also replace previous instances of the constants with the new enum values.
Signed-off-by: Wambui Karuga
---
blame.c | 8
blame.h | 12 +++-
builtin/blame.c | 17 -
3 files change
Hello Jonathan!
My name is Wambui and I'm one of the applicants in the current round of
Outreachy applications. I wanted to write an initial email to introduce
myself since I'm interested in working on your mentored projects!
I have been going through the mailing list threads about Out
On Fri, Sep 27, 2019 at 06:18:58PM -0400, Jeff King wrote:
> On Thu, Sep 26, 2019 at 11:44:48PM +0200, SZEDER Gábor wrote:
>
> > All that was over a year and a half ago, and these limitations weren't
> > a maintenance burden at all so far, and nobody needed that escape
> > hatch.
> I'm actually s
Hi Emily,
On Mon, 7 Oct 2019, Emily Shaffer wrote:
> The community discussed the list of microprojects for applicants to
> try in this mailing list thread:
> https://public-inbox.org/git/20190916184208.gb17...@google.com/
An email thread is immutable, so maybe you want to transfer at least
some
On Sun, Oct 06, 2019 at 01:32:54AM +0530, Rajni Jha wrote:
> Hello!
Welcome! Thank you for introducing yourself and please don't hesitate to
ask any questions you may have.
>
> I am an outreachy applicant and I am looking forward to working with git
> for my outreachy internship
On 10/4/2019 4:52 AM, Johannes Schindelin wrote:
> Hi George,
>
> if you have Visual Studio, you could also check out the `vs/master`
> branch of https://github.com/git-for-windows/git and build Git inside
> Visual Studio. The tests can still be run in Git Bash (the regular one
> this time, no nee
alkthrough. So now
> > I’m stuck on the “make” step to see if I added the psuh feature in
> > correctly. I also noticed when I looked at the INSTALL page on github it
> > made it seem like maybe installing it through the website wasn’t the right
> > idea? Maybe that’s why I
t. Should I install
something similar to iTerm instead on windows and just start fresh? ty.
George!
On Thu, Oct 3, 2019 at 11:14 AM Emily Shaffer wrote:
Hi George,
Great to hear that you're walking through the MyFirstContribution
tutorial - that's a great introduction to how the
t fresh? ty.
> >
> > George!
> >
> > On Thu, Oct 3, 2019 at 11:14 AM Emily Shaffer
> > wrote:
> >>
> >> Hi George,
> >>
> >> Great to hear that you're walking through the MyFirstContribution
> >> tutorial - that's a gr
through the MyFirstContribution
>> tutorial - that's a great introduction to how the Git project gets
>> stuff done.
>>
>> This is my first time mentoring for Outreachy, but as I understand it,
>> you will start by doing a microproject so everybody can see if you
Johannes Schindelin wrote:
> On Tue, 24 Sep 2019, Eric Wong wrote:
> > Johannes Schindelin wrote:
> > > On Mon, 16 Sep 2019, Emily Shaffer wrote:
> > > > - try and make progress towards running many tests from a single test
> > > >file in parallel - maybe this is too big, I'm not sure if we
Eric Wong writes:
> C is fine for unit tests, and maybe we can use more unit tests
> and less integration tests.
Nicely put. I often find it somewhat disturbing that what some of
the t/helper/ tests are trying to exercise is at too low a level
that the distance from the real-world observable ef
Jeff King writes:
> On Tue, Sep 24, 2019 at 04:25:45PM +0200, Johannes Schindelin wrote:
>
>> > I think it could make sense for merge-index to be able to directly run
>> > the merge-one-file code[1]. But I think we'd want to keep its ability to
>> > run an arbitrary script, and for people to call
On Thu, Sep 26, 2019 at 11:44:48PM +0200, SZEDER Gábor wrote:
> All that was over a year and a half ago, and these limitations weren't
> a maintenance burden at all so far, and nobody needed that escape
> hatch.
>
> Well, nobody except me, that is :) When I saw back then that t1510
> saves the s
On Thu, Sep 26, 2019 at 03:12:15PM +0200, Christian Couder wrote:
> On https://www.outreachy.org/apply/project-selection/#git it looks
> like we will only have 1 intern as the title of our section is "Git -
> 1 intern". I wonder if it's because only funding for 1 intern has been
> secured or if th
On Thu, Sep 26, 2019 at 09:32:35PM +0200, Johannes Schindelin wrote:
> Hi,
>
> On Thu, 26 Sep 2019, SZEDER Gábor wrote:
>
> > On Mon, Sep 23, 2019 at 08:07:09PM +0200, SZEDER Gábor wrote:
> > > Here is one more idea for microprojects:
> > >
> > > Find a group of related preprocessor constants a
On Thu, Sep 26, 2019 at 09:39:58PM +0200, Johannes Schindelin wrote:
> Hi,
>
> On Thu, 26 Sep 2019, SZEDER Gábor wrote:
>
> > On Thu, Sep 26, 2019 at 01:04:48PM +0200, Johannes Schindelin wrote:
> > > > > > > Also, things like the code tracing via `-x` (which relies on Bash
> > > > > > > function
Hi,
On Thu, 26 Sep 2019, SZEDER Gábor wrote:
> On Thu, Sep 26, 2019 at 01:04:48PM +0200, Johannes Schindelin wrote:
> > > > > > Also, things like the code tracing via `-x` (which relies on Bash
> > > > > > functionality in order to work properly,
> > > > >
> > > > > Not really.
> > > >
> > > > To
Hi,
On Thu, 26 Sep 2019, SZEDER Gábor wrote:
> On Mon, Sep 23, 2019 at 08:07:09PM +0200, SZEDER Gábor wrote:
> > Here is one more idea for microprojects:
> >
> > Find a group of related preprocessor constants and turn them into an
> > enum. Also find where those constants are stored in varia
On Thu, Sep 26, 2019 at 01:04:48PM +0200, Johannes Schindelin wrote:
> > > > > Also, things like the code tracing via `-x` (which relies on Bash
> > > > > functionality in order to work properly,
> > > >
> > > > Not really.
> > >
> > > To work properly. What I meant was the trick we need to play wi
Hi Peff and everyone,
On https://www.outreachy.org/apply/project-selection/#git it looks
like we will only have 1 intern as the title of our section is "Git -
1 intern". I wonder if it's because only funding for 1 intern has been
secured or if there is another reason.
Also I am not sure how peopl
Hi Eric,
On Tue, 24 Sep 2019, Eric Wong wrote:
> Johannes Schindelin wrote:
> > On Mon, 16 Sep 2019, Emily Shaffer wrote:
> > > - try and make progress towards running many tests from a single test
> > >file in parallel - maybe this is too big, I'm not sure if we know how
> > >many of o
Hi,
On Mon, 23 Sep 2019, SZEDER Gábor wrote:
> On Wed, Sep 04, 2019 at 03:41:15PM -0400, Jeff King wrote:
> > The project page has a section to point people in the right direction
> > for first-time contributions. I've left it blank for now, but I think it
> > makes sense to point one (or both) o
Hi,
On Mon, 23 Sep 2019, SZEDER Gábor wrote:
> On Mon, Sep 23, 2019 at 02:47:23PM +0200, Johannes Schindelin wrote:
> >
> > On Tue, 17 Sep 2019, SZEDER Gábor wrote:
> >
> > > On Tue, Sep 17, 2019 at 01:23:18PM +0200, Johannes Schindelin wrote:
> > > > Also, things like the code tracing via `-x` (
On Mon, Sep 23, 2019 at 08:07:09PM +0200, SZEDER Gábor wrote:
> Here is one more idea for microprojects:
>
> Find a group of related preprocessor constants and turn them into an
> enum. Also find where those constants are stored in variables and
> in structs and passed around as function pa
project?
>
> Besides discussing the likelihood of patches being accepted/rejected,
> should we record the result of discussion somewhere (or, if only the
> mentor should give their ideas, for me to write in more detail)? I don't
> recall a place in the Outreachy form to write thi
do you think that there is enough likelihood of
acceptance that we can move ahead with my proposed project?
Besides discussing the likelihood of patches being accepted/rejected,
should we record the result of discussion somewhere (or, if only the
mentor should give their ideas, for me to write
On Tue, Sep 24, 2019 at 04:25:45PM +0200, Johannes Schindelin wrote:
> > I think it could make sense for merge-index to be able to directly run
> > the merge-one-file code[1]. But I think we'd want to keep its ability to
> > run an arbitrary script, and for people to call merge-one-file
> > separa
Hi Peff,
On Mon, 23 Sep 2019, Jeff King wrote:
> On Mon, Sep 23, 2019 at 02:47:23PM +0200, Johannes Schindelin wrote:
>
> > The evaluation of the lazy prereq is indeed not different between Bash
> > or dash. It is nevertheless quite disruptive in the trace of a test
> > script, especially when it
Hi Peff,
On Mon, 23 Sep 2019, Jeff King wrote:
> On Tue, Sep 17, 2019 at 01:23:18PM +0200, Johannes Schindelin wrote:
>
> > The only slightly challenging aspect might be that `merge-one-file` is
> > actually not a merge strategy, but it is used as helper to be passed to
> > `git merge-index` via
Johannes Schindelin wrote:
> On Mon, 16 Sep 2019, Emily Shaffer wrote:
> > - try and make progress towards running many tests from a single test
> >file in parallel - maybe this is too big, I'm not sure if we know how
> >many of our tests are order-dependent within a file for now...
>
>
On 23/09/2019 20:40, Jeff King wrote:
On Fri, Sep 20, 2019 at 06:47:01PM -0700, Emily Shaffer wrote:
"""
"Did You Mean..?"
There are some situations where it's fairly clear what a user meant to
do, even though they did not do that thing correctly. For example, if a
user runs `git commit` with
gt; > [dropping unpack-objects]
> > Maybe that would be worth making part of the project?
>
> I'm reluctant to do so because I don't want to increase the scope too
> much - although if my project has relatively narrow scope for an
> Outreachy project, we can
public chat. If you are
> > asked for username, pick any username! You will not need a password to
> > join this chat.
> >
> > Git mailing list - Follow this link to join this project's public
> > chat.
>
> where the IRC link goes to Freenode's webch
e9c147f3023225f8a6f72e303
>
> Maybe that would be worth making part of the project?
I'm reluctant to do so because I don't want to increase the scope too
much - although if my project has relatively narrow scope for an
Outreachy project, we can do so. As for eliminating the util
On Fri, Sep 20, 2019 at 06:47:01PM -0700, Emily Shaffer wrote:
> """
> "Did You Mean..?"
>
> There are some situations where it's fairly clear what a user meant to
> do, even though they did not do that thing correctly. For example, if a
> user runs `git commit` with tracked, modified, unstaged f
On Tue, Sep 17, 2019 at 05:10:43PM +0200, Christian Couder wrote:
> > Nice projects, all. There are a couple more ideas on
> > https://github.com/gitgitgadget/git/issues, they could probably use some
> > tagging.
>
> Thanks! Maybe we should have a page with Outreachy
.com/community.
The other proposal is from Christian, who wrote:
> Please introduce yourself on the public project chat:
>
> a mailing list - Once you join the project's communication
> channel, the mentors have some additional instructions for you to
> follow:
>
On Fri, Sep 20, 2019 at 10:04:48AM -0700, Jonathan Tan wrote:
> > I'm happy to discuss possible projects if anybody has an idea but isn't
> > sure how to develop it into a proposal.
>
> I'm new to Outreachy and programs like this, so does anyone have an
> op
On Mon, Sep 23, 2019 at 02:47:23PM +0200, Johannes Schindelin wrote:
> The evaluation of the lazy prereq is indeed not different between Bash
> or dash. It is nevertheless quite disruptive in the trace of a test
> script, especially when it is evaluated for a test case that is skipped
> explicitly
On Tue, Sep 17, 2019 at 01:23:18PM +0200, Johannes Schindelin wrote:
> The only slightly challenging aspect might be that `merge-one-file` is
> actually not a merge strategy, but it is used as helper to be passed to
> `git merge-index` via the `-o ` option, which makes it slightly
> awkward to be
On Wed, Sep 04, 2019 at 03:41:15PM -0400, Jeff King wrote:
> The project page has a section to point people in the right direction
> for first-time contributions. I've left it blank for now, but I think it
> makes sense to point one (or both) of:
>
> - https://git-scm.com/docs/MyFirstContributio
> No need for user-facing benefits. Refactoring or improving the code in
> other useful ways are very good subjects (as I already said in my
> reply to Emily and Dscho).
Thanks!
> I think this is really great, both the idea and the description! No
> need for more details.
Thanks! I've just submi
On Mon, Sep 23, 2019 at 02:47:23PM +0200, Johannes Schindelin wrote:
> Hi,
>
> On Tue, 17 Sep 2019, SZEDER Gábor wrote:
>
> > On Tue, Sep 17, 2019 at 01:23:18PM +0200, Johannes Schindelin wrote:
> > > Also, things like the code tracing via `-x` (which relies on Bash
> > > functionality in order t
On Mon, Sep 23, 2019 at 3:35 PM Emily Shaffer wrote:
>
> On Fri, Sep 20, 2019 at 10:04:48AM -0700, Jonathan Tan wrote:
>
> > I'm new to Outreachy and programs like this, so does anyone have an
> > opinion on my draft proposal below? It does not have any immediate
>
Hi,
On Tue, 17 Sep 2019, Christian Couder wrote:
> On Tue, Sep 17, 2019 at 1:28 PM Johannes Schindelin
> wrote:
> > On Mon, 16 Sep 2019, Emily Shaffer wrote:
> >
> > > - reduce/eliminate use of fetch_if_missing global
>
> I like this one!
It looks as if a (non
Hi,
On Tue, 17 Sep 2019, SZEDER Gábor wrote:
> On Tue, Sep 17, 2019 at 01:23:18PM +0200, Johannes Schindelin wrote:
> > Also, things like the code tracing via `-x` (which relies on Bash
> > functionality in order to work properly,
>
> Not really.
To work properly. What I meant was the trick we n
is really soon.
> > I'm happy to discuss possible projects if anybody has an idea but isn't
> > sure how to develop it into a proposal.
>
> I'm new to Outreachy and programs like this, so does anyone have an
> opinion on my draft proposal below? It does not
but isn't
> > sure how to develop it into a proposal.
>
> I'm new to Outreachy and programs like this, so does anyone have an
> opinion on my draft proposal below? It does not have any immediate
> user-facing benefit, but it does have a definite end point.
I'd apprec
> Prospective mentors need to sign up on that site, and should propose a
> project they'd be willing to mentor.
[snip]
> I'm happy to discuss possible projects if anybody has an idea but isn't
> sure how to develop it into a proposal.
I'm new to Outreachy and pr
ch Git can use if present rather than
> >checking system local time
>
> Nice projects, all. There are a couple more ideas on
> https://github.com/gitgitgadget/git/issues, they could probably use some
> tagging.
Thanks! Maybe we should have a page with Outreachy microprojects on
h
On Tue, Sep 17, 2019 at 01:23:18PM +0200, Johannes Schindelin wrote:
> Also, things like the code tracing via `-x` (which relies on Bash
> functionality in order to work properly,
Not really.
> and which _still_ does not work
> as intended if your test case evaluates a lazy prereq that has not be
Hi Emily,
On Mon, 16 Sep 2019, Emily Shaffer wrote:
> Jonathan Tan, Jonathan Nieder, Josh Steadmon and I met on Friday to
> talk about projects and we came up with a trimmed list; not sure what
> more needs to be done to make them into fully-fledged proposals.
Thank you for doing this!
> For st
On Mon, Sep 16, 2019 at 04:13:49PM -0700, Jonathan Nieder wrote:
> Most tests use "setup" or "set up" in the names of test assertions
> that are required by later tests. It's very helpful for debugging and
> maintenance to be able to skip or reorder some tests, so I've been
> able to rely on this
SZEDER Gábor wrote:
> On Mon, Sep 16, 2019 at 11:42:08AM -0700, Emily Shaffer wrote:
>> - try and make progress towards running many tests from a single test
>>file in parallel - maybe this is too big, I'm not sure if we know how
>>many of our tests are order-dependent within a file for n
On Mon, Sep 16, 2019 at 11:42:08AM -0700, Emily Shaffer wrote:
> - try and make progress towards running many tests from a single test
>file in parallel - maybe this is too big, I'm not sure if we know how
>many of our tests are order-dependent within a file for now...
Forget it, too many
Emily Shaffer wrote:
> Jonathan Tan, Jonathan Nieder, Josh Steadmon and I met on Friday to talk
> about projects and we came up with a trimmed list; not sure what more
> needs to be done to make them into fully-fledged proposals.
> For the longer projects, we came up with a few more:
> - ad
On Fri, Sep 13, 2019 at 04:51:49PM -0400, Jeff King wrote:
> On Fri, Sep 13, 2019 at 01:03:17PM -0700, Jonathan Tan wrote:
>
> > > Do we have interested mentors for the next round of Outreachy?
> > >
> > > The deadline for Git to apply to the program is Sept
On Fri, Sep 13, 2019 at 01:03:17PM -0700, Jonathan Tan wrote:
> > Do we have interested mentors for the next round of Outreachy?
> >
> > The deadline for Git to apply to the program is September 5th. The
> > deadline for mentors to have submitted project descriptio
> Do we have interested mentors for the next round of Outreachy?
>
> The deadline for Git to apply to the program is September 5th. The
> deadline for mentors to have submitted project descriptions is September
> 24th. Intern applications would start on October 1st.
>
> If
while people do get a feel of the community and
> general workflow, they don't necessarily get a feel of the actual git
> internal codebase.
> - Since I don't see a git-gui related project worth being into the
> Outreachy program, it essentially means they will likel
actual git
internal codebase.
- Since I don't see a git-gui related project worth being into the
Outreachy program, it essentially means they will likely not work on
anything related to their project.
- Git-gui is essentially a wrapper on top of git, so people won't get
exposure to
On Fri, Sep 6, 2019 at 11:40 PM Jeff King wrote:
>
> I just wrote a response to Emily, but I think a lot of it applies to
> you, as well.
With the exception of course that Emily can definitely write better
code than my attempted hacks
> In particular, I think both of you are a bit newer to the p
On Fri, Sep 06, 2019 at 04:55:46AM -0700, Carlo Arenas wrote:
> I'm interested to mentor/help too, but I am definitely not a (some
> people would even argue against "reliable") contributor but I might be
> better than nothing and could pass my "lessons learned" along, so
> hopefully next contribut
ect for the intern. You can take a look at previous Outreachy and
GSoC proposals[1] to get the general idea, and then think about some
area you feel comfortable working in. You're welcome to send ideas or
drafts to the list to get feedback.
If you're feeling overwhelmed (or even if you're
I'm interested to mentor/help too, but I am definitely not a (some
people would even argue against "reliable") contributor but I might be
better than nothing and could pass my "lessons learned" along, so
hopefully next contributors are less of a pain to deal with than I am
Carlo
On Wed, Sep 04, 2019 at 03:41:15PM -0400, Jeff King wrote:
> On Tue, Aug 27, 2019 at 01:17:57AM -0400, Jeff King wrote:
>
> > Do we have interested mentors for the next round of Outreachy?
> >
> > The deadline for Git to apply to the program is September 5th. The
> >
On Wed, Sep 4, 2019 at 9:41 PM Jeff King wrote:
>
> Funding is still up in the air, but in the meantime I've tentatively
> signed us up (we have until the 24th to have the funding committed).
> Next we need mentors to submit projects, as well as first-time
> contribution micro-projects.
Great! Th
On Tue, Aug 27, 2019 at 01:17:57AM -0400, Jeff King wrote:
> Do we have interested mentors for the next round of Outreachy?
>
> The deadline for Git to apply to the program is September 5th. The
> deadline for mentors to have submitted project descriptions is September
&g
сб, 31 авг. 2019 г. в 10:58, Christian Couder :
>
> On Tue, Aug 27, 2019 at 7:17 AM Jeff King wrote:
> >
> > Do we have interested mentors for the next round of Outreachy?
>
> I am interested to co-mentor.
I am not ready to give the answer right now, but I will definitely
On Tue, Aug 27, 2019 at 7:17 AM Jeff King wrote:
>
> Do we have interested mentors for the next round of Outreachy?
I am interested to co-mentor.
> The deadline for Git to apply to the program is September 5th. The
> deadline for mentors to have submitted project descriptions
Do we have interested mentors for the next round of Outreachy?
The deadline for Git to apply to the program is September 5th. The
deadline for mentors to have submitted project descriptions is September
24th. Intern applications would start on October 1st.
If there are mentors who want to
Hi everyone,
Today is officially the last day of my Outreachy internship.
I wanted to say a few things about my experience and future of the
project I worked on.
Project was "Turn git add -i into built-in" with Johannes Schindelin
as my mentor.
I truly had amazing time, I learned so
1 - 100 of 277 matches
Mail list logo
