Re: submitting a patch questions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jan 17, 2007 at 10:37:27AM +0200, Ramagudi Naziir wrote:
> I'm writing a new driver.
> This is a new file, entirely, not changed code.
> when I do a "git diff" I don't see it.

When you haven't told git about the file (i.e.: git add, git commit),
it will not track it and will not show a diff.

> How do I make the patch then ?

  git add mynewfile
  git commit mynewfile Kconfig-for-mynewfile Makefile-for-mynewfile \
      Documentation-for-my-newfile
  git diff HEAD^ HEAD

> Besides that, any changes to Kconfig, Makefile and documentations
> should be send as usual in the patch ?

Yes, otherwise the driver won't work. When the patch gets too large,
documentation can be send as a separate patch.


Erik

-- 
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux