public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: insight@sourceware.org
Cc: Dave Murphy <davem@devkitpro.org>
Subject: Re: MinGW patches for Insight
Date: Fri, 08 Feb 2008 18:05:00 -0000	[thread overview]
Message-ID: <200802081304.01150.vapier@gentoo.org> (raw)
In-Reply-To: <47AC8FC4.8070204@devkitpro.org>

[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]

On Friday 08 February 2008, Dave Murphy wrote:
> I'm still not sure how best to format the changelog entries. Should I be
> sending a patchset for each directory where changes are made?

you do it based upon the ChangeLog files that already exist.  look at the file 
you change, and then walk up directories until you hit the first ChangeLog 
file.

>   2008-02-07  Dave Murphy  <davem@devkitpro.org>
>
>         *configure.ac
>         set tcl configdir to win under mingw32

if you look at the existing ChangeLog entries, you'll see these are formatted 
wrong.  it's something like:
	* file (relevant scope in file where applicable): Description of change.

>         *gdb/configure
>         regenerate

while you are supposed to say you regenerated things, you dont actually 
include the changes to configure in patches that get posted to mailing lists 
and such.  generated files are not interesting and tend to contain a lot of 
noise.

> --- gdb/configure.ac    13 Jan 2008 12:23:05 -0000      1.64
> +++ gdb/configure.ac    8 Feb 2008 15:42:43 -0000
> @@ -1445,7 +1445,7 @@
>  AC_SUBST(WIN32LDAPP)
>  
>  case "${host}" in
> -*-*-cygwin*)
> +*-*-cygwin* | *mingw32* )
>      configdir="win"
>      ;;
>  *)

what about 64bit mingw ?

> --- gdb/gdbtk/generic/gdbtk-interp.c    23 Dec 2005 18:23:16 -0000      1.8
> +++ gdb/gdbtk/generic/gdbtk-interp.c    6 Feb 2008 03:50:50 -0000
> @@ -34,6 +34,12 @@
>  #include "tk.h"
>  #include "gdbtk.h"
>  
> +#ifdef __MINGW32__
> +       #define WIN32_LEAN_AND_MEAN
> +       #include <windows.h>
> +#endif

never put whitespace before the #:
#ifdef __MINGW32__
# define WIN32_LEAN_AND_MEAN
# include <windows.h>
#endif
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2008-02-08 18:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07  8:35 Dave Murphy
2008-02-08 17:24 ` Dave Murphy
2008-02-08 18:05   ` Mike Frysinger [this message]
2008-02-08 23:17     ` Dave Murphy
2008-02-08 23:34       ` Mike Frysinger
2008-02-09  0:03       ` Keith Seitz
2008-02-09  1:24         ` Keith Seitz
2008-02-09  1:55           ` Dave Murphy
2008-02-09  2:32           ` Dave Murphy
2008-03-03 23:28             ` Keith Seitz
2008-03-12 12:31               ` Dave Murphy
2008-02-09  1:51         ` Dave Murphy

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200802081304.01150.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=davem@devkitpro.org \
    --cc=insight@sourceware.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.
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).