[haiku-gsoc] Re: 3D HW accel Repo issues
- From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-gsoc@xxxxxxxxxxxxx
- Date: Tue, 23 May 2017 07:40:43 +0200
On Mon, May 22, 2017 at 07:50:01PM -0500, kallisti5 wrote:
On 2017-05-22 17:41, James Taylor wrote:
Hey guys,
Apparently there's been an issue about how I organized the repo for
Vivek to work in for his project. I did so to try to make it as easy
for him to work in as possible, but apparently that was a bad idea. So
my question is, how would you suggest I roll back those changes?
This is git, you don't need to roll back anything. Just create a new
branch and experiment in other directions. All your attempts are tracked
and you can get back to them at any time.
This is the main power of git when compared to SVN, where once you press
the "commit" button, everything is set in stone for eternity. I spend a
lot of time rewriting my commit history and cleaning things up, but it
means at the end I can provide:
1) A log of my development work, showing what I tried, which approaches
failed, etc.
2) A clean log of only the changes that works, with the minilal set of
changes, and in a logical order, easy to follow for other people.
This makes git an awesome tool for documenting the development process,
almost like a wiki where you would track everything you do.
Vivek, I think the missing piece is a rough technical write up
of what your plans are.
This goes to all GSOC students. Please spam this mailing list
(and IRC) to your heart's content if you have any question at all
about things. That's what it's here for :-)
In more general terms, we are currently in the "community bonding"
period. This means you don't have to be writing code at this point, and
there is time to discuss your project, refine the design, and prepare a
plan for action. It is fine if you feel that doing so requires making
some experiments with the code to understand its architecture, but the
main goal at this point should be setting up and refining a plan for the
summer. We can always adjust it later, but it is nice to know where we
are headed: where is the code written, how and when does it get integrated in
Haiku, how can the mentors and other people review or test it, etc.
--
Adrien.
Other related posts:
